New RunLLM response generated: >>>*# Question* Hi team. I am looking for design documentation of the Signals feature. Want to understand how it works in detail. What problem I am facing. we are sending signals to continue the workflow if any of its task fail. However sometimes we are getting

FlyteInvalidInputException

. What we understand is that signal Gate Node is not ready to receive the signal and hence the failure # Answer The Signals feature in Flyte allows for dynamic, runtime control of workflow executions by integrating signal-driven gates. This feature is designed to enable workflows to pause and wait for external inputs or conditions before proceeding. According to the RFC on Runtime Workflow Control Using Signals and Gate Nodes, signals can be used to trigger gates in workflows, allowing for manual interaction or programmatic input to control the flow of execution. The

FlyteInvalidInputException

you are encountering may occur if the signal is sent before the gate node is ready to receive it. This can happen if the workflow execution has not yet reached the point where it is waiting for the signal. To avoid this, ensure that the signal is sent only after the workflow has reached the gate node and is actively waiting for the signal. You can use the Flyte UI or the

FlyteRemote

API to check the status of the workflow and confirm that it is in the correct state to receive the signal. Would you like more details on how to handle signals or troubleshoot this issue further? Sources: - RFC on Runtime Workflow Control Using Signals and Gate Nodes - Waiting for External Inputs Slack Link https://.slack.com/archives/CP2HDHKE1/p1730184896.169739 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.