Note: this quick start guide is of the latest version of the pilot but does not contain the features that will be in the official launch. See our product roadmap for the upcoming features to the pilot. If you'd like to be added to the pilot then let us know via the in-app chat.
Creating your flow error monitoring job
From the main Gearset sidebar menu under Error monitoring category, click on Flow error monitoring.
From the welcome screen, click on
Begin setupChoose the Salesforce org you want to monitor for flow errors and click next
Follow the setup instructions to use the generated Gearset email inbox that will be monitored for flow errors
Click
Finish setup
We recommend adding additional recipients to ensure that Apex Exception emails are still received.
During setup, you will be prompted to update the Apex Exception Email recipient to use the Gearset-generated email address. Both Flow and Apex error emails will be sent to the Gearset inbox.
You can add an existing Salesforce user to the recipient list, or enter extra recipients in the External Email Addresses field, separated by a semi-colon.
Adding Slack and MS Teams notifications
Once a job has been created you can add Slack and MS Teams notifications to receive a channel alert when a Flow error occurs. See our adding Slack and MS Teams notifications documentation for step-by-step instructions.
Flow error results
Gearset will automatically begin to monitor the inbox for any flow error emails.
Sorting and filtering options
Flows can be sorted by error count, first and last seen error dates, users impacted and by Flow name
Flows with errors can also be filtered by date range with a number of presets or choosing your own custom date range
Free text filtering can search for any Flow name, element or error type within the results currently displayed in the selected time range.
Errors are grouped by the Flow name which can be expanded to show the breakdown of error types and instance details.
First seen shows the first time a Flow error report received within the selected time range. Note: If the monitoring job was created after the selected time range it'll only display the first seen date since the job was created within that range.
Last seen shows the last time an error report was received in the selected time range with job creation date also taken into account when applicable.
Users displays the number of users who triggered the error (current user from the Flow interview).
Error count is the total number of times an error was received.
At the Flow level the numbers are in relation to the stats at the top of the page.
Expanding a Flow row shows a breakdown for that Flow of the different problem types and Flow elements with date, error count, users impacted metrics. Clicking on View errors provides access to the error reports for those errors. The numbers and percentages for errors are in relation to the Flow.
