Q&A form the Live Session | Error Handling and Debugging: Troubleshooting Your Automations

Q: When do you know to use Quick Flows over Quick Automate?

A: A simple way to think about it: Automate is for complex, enterprise-grade business processes — things like claims processing or invoice processing — where you need end-to-end governance, scheduling, API triggers, and separate monitoring. Flows are for simpler, personal productivity automations, like summarizing a document and sending an email. Automate is the enterprise-grade tool for complex automations; Flows is your personal productivity automation tool.


Q: Will knowledge base features be available in Quick Automate?

A: You can already use knowledge bases in Quick Automate through custom agents. This capability is currently in private beta — if you’d like access, reach out and the team can get you onboarded. It should be available in GA very soon.


Q: For any exception (system or business), do you get a screenshot at the point it fails — for example, for a blank stock name?

A: There is an action available where you can proactively take a screenshot at a specific stage — you can add a “grab screenshot” step in your catch block to capture the screen at the point of failure. For browser-related actions, screenshots are automatically captured in the logs for every single browser action that runs. However, for non-browser exceptions (like a blank stock name, which occurs before the browser even opens), a screenshot may not be as helpful. Either way, you can proactively add a screenshot action, or the logs will capture screenshots for any browser-related steps automatically.