Replies: 2 comments
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
still no resolution. leaving open. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
According to the documentation, the
description
property for an input in a custom action is required:For workflows that are using the
workflow_dispatch
this makes sense since the description is displayed to the user. But for a custom action, where is this property ever used? Is it ever displayed to the user? I assumed that it would be if you attempted to call the action and didn't provide a required input, but so far I can't tell from the docs, or in practice where this data is displayed to the user. Is it only in the raw logs?Interestingly, for inputs in a
workflow_dispatch
event, thedescription
property isn't required even though it's used... 😖Beta Was this translation helpful? Give feedback.
All reactions