Flows: FAQs & Troubleshooting
Find answers to common flow questions and resolve known configuration and test issues.
Last updated
Was this helpful?
Find answers to common flow questions and resolve known configuration and test issues.
This page answers common questions about building and running flows. Use the troubleshooting steps when the product shows a specific status or warning.
A flow belongs to the project where you create it. It is not available in other projects.
Choose a trigger:
Start manually starts the flow when a user launches it.
Start through Agent lets an AI agent start the flow.
Start via trigger starts from an external event. This option is still in development.
Yes. Each flow is available as a skill with the flow's name and description. Add it through the agent's Add Skill dialog, or use the Start through Agent trigger.
Define fields in Input Schema. During Try Out, provide a value for each field. You can enter values in JSON Grid or as raw JSON.
Store API keys, tokens, and other credentials as Secrets. Reference them in task settings with $secret.{variable_name}.
Changes remain in a draft until you select Publish. Publishing makes that draft the current published version.
A required task setting is empty. Select the task, complete the required setting, and test the flow again before publishing.
The run may be waiting at a User Approval task. Enter the requested answer, then select Continue. Select Cancel to stop the run.
Open Execution Log after the run. It lists each task and its result. Review the input values and task configuration, then run the test again.
Open Version History and select Revert Draft Changes. This restores the published version.
Need configuration details? See Build a flow and Test and publish flows.
Maintained by Abhishek Paul
AI-assisted, human-approved

Last updated
Was this helpful?
Was this helpful?

