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 to help manage when and where errors should be displayed.
Three factors can determine where an error is bucketed and when it may move to a different category:
The category selected by you
The default behaviour of the category
The triggering of a configured notification rule (e.g. a notification rule that sends an alert when an error occurs on a specific Flow over 100 times within 30 minutes).
For more information on configuring Slack and/or MS Teams error notification rules see our notification rules documentation.
Assigning error categories and their definitions
To enable easier management of errors you can move specific Flow and Apex errors to one of five preset categories which deal with errors in different ways.
Active: These are typically new or recent alerts that you’re either actively triaging or are waiting to be reviewed and moved to another category if applicable. If an error that has never been previously encountered is detected it will, by default, be placed in the
Activecategory.Snoozed: Errors marked as
Snoozedwill temporarily pause notifications for a chosen period of time and, once the snooze period has ended, will automatically return to theActivecategory when another instance of the error reoccurs. This category is designed for errors that you wish to pause notifications for whilst you investigate the issue further or will review after a given time period when more convenient.Resolved: Errors that were reviewed, determined to require a fix, and the underlying issue was actively actioned 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. However,
Archivederrors are still impacted by any configured notification rules so 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 you don't want to automatically return to an
Activestate - regardless of a notification rule being triggered. These can be errors you know are due to a 3rd party automation process and require no intervention. Any subsequent occurrences of this Flow element error will be automatically marked as ignored.
Moving errors to a category
You can move an error between any category as many or as few times as you wish. 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
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.