Enterprise customers can now connect their Retool organization to Sentry and Datadog for workflow error reporting and event logging. We’ve also made some major improvements to the workflows run panel that make it easier for all customers to find and inspect a particular workflow run and reproduce errors.
Run panel improvements are available for all customers on cloud and the latest stable. Check them out now or read more about them here!
The error reporting and event logging feature is in beta for customers on the Q2 ‘25 3.196.0 stable release and will be available in GA in the Q3 '25 stable release. In the interim, self-hosted customers on the stable release cycle should fill out this form for access. Cloud customers can toggle this feature on now in the advanced settings > beta page by searching for “Enable exporting workflow logs and observability events.”
Take a look at this loom and our documentation for an in-depth walkthrough, or read through some of the FAQ’s below!
When should I think about monitoring Workflow events in an external observability provider?
- Your organization has a high volume of workflow runs that your team would prefer to monitor systematically outside of the Workflows run panel UI.
- Your organization is on cloud and would like to retain a record of workflow run events beyond the 90 day retention period.
What are the major run panel improvements I should look out for?
- Added filtering historical runs based on timestamp and workflow run ID in the Run panel.
- Added searching logs by block name in the Run panel.
- Added filtering blocks by type in the Run panel.
- Moved the "Use as Example JSON" button to the top of the Data tab.
- Added the ability to download JSON data from the JSON tab of block outputs or from the JSON tab of the Run panel.
- Added workflowRunContext to the Input tab of block outputs.
- Added endedAtEpochMs to workflowRunContext in the Input tab of block outputs.
How should I change my existing workflows to take advantage of these improvements?
- Be sure to reference Workflow Run ID and the workflow’s Ended At properties in the body of your global error handler with workflowContext.currentRun.workflowRunId and workflowContext.lastRun.endedAtEpochMs. You can also emit both properties by default by connecting your Retool organization to DataDog or Sentry. Having the workflowRunId and timestamp handy at debug time will allow you to quickly filter workflow runs to the errored workflow run.
- Name all of your blocks descriptively to make them easy to search for in the run panel.
- Reproduce workflow errors manually by clicking “Use as Test JSON Parameters” from the start trigger’s data tab in the run panel. This will upsert the parameters passed in a particular workflow run as test JSON parameters in the start trigger block.
Happy building! 