A large number of Flow and/or Apex errors can be regularly generated and sent by Salesforce leading to challenges in managing and separating out errors that are new, those that are important to fix and those which can be safely disregarded.
Gearset provides 5 out of the box preset categories or 'buckets' to help manage the reviewing and handling Flow errors - similar to how you might create email inbox rules.
Gearset's five error categories and their definitions
To enable easier management of errors you can move specific Flow and Apex errors to one of five pre-set categories which deal with errors in different ways. You can do this either manually or create rules that automatically place errors into one of the five pre-sets if they match the rule conditions.
Active: By default, all new alerts will be placed in the
Activebucket.Snoozed: Errors manually moved to
Snoozedwill temporarily pause Slack or Teams notifications for a chosen period of time and, once the snooze period has ended, will move back to theActivecategory when another instance of the error reoccurs. This category is useful when you want to pause notifications whilst you investigate issues or will review further after a given time period.Resolved: Errors that were actively acted upon and resolved by you or your team (e.g. shipping a fix to Production). Should the same error reoccur after being marked as
Resolvedit will return to theActivecategory for further investigation.Archived: Errors that were reviewed and determined to require no further follow-up or you've decided won't be fixed. These can often be low frequency/volume transient errors which will resolve themselves or don't impact the business or user in any meaningful way (e.g. simple validation errors).
Note: If you've created alert notification rules -
Archivederrors will automatically return to theActivecategory if a notification rule’s criteria is met (e.g. a high volume of errors occur within a specified timeframe for a specified Flow element).
Ignore: Errors that will remain in
Ignoreand are not impacted by any other events. For example, errors that you know are due to a 3rd party automation process and require no intervention.
Manually moving errors to a pre-set error category/bucket
To move an error into a specific category, simply:
Click on the error from the list of results to see the details of that error
From the side panel on the right, under
Error category, click the dropdown and choose the category the error will be moved into.
Snoozing errors: configuring duration
Errors marked as Snoozed will remain in that category until the selected time period ends (e.g. 24 hours) and return to the Active category once a new error occurs after that point. You can also manually cancel a specified snooze period which will automatically recategorize the error as Active.
Once an error has been categorised it will then appear under that category in the results page.
You can move an error to another category at any point by following the previous steps.
Creating rules to automatically categorize Flow or Apex errors
Not all Flow and Apex errors are critical or important. You may have a number of well understood errors that are simply due to user error (e.g. field validation error), and if the correct input is given the error won't occur. For these types of errors you will want those errors to bypass the Active inbox and go directly to Archived or Ignore. You can do this by creating rules to handle this scenario.
From the panel on the right when viewing an error:
Click on
Add categorization rule.Enter a name for the rule.
Enter the string(s) that you want Gearset to check for in the content of the error email.
Choose the category or bucket the error email should be placed in (i.e.
Resolved,IgnoreorArchive).Click
Save rule.
