Gearset's setup process configures Salesforce org limit monitoring and error monitoring for Apex and Flow in parallel under a single setup process as they use different mechanisms to monitor for limits or errors.
To create your job:
Click
Begin setupif you've not created a monitoring job previously, or go to theActionsmenu dropdown and click onAdd a new jobif a member of your team has already created a monitoring job.Choose the Salesforce org that you wish to monitor for errors. (Note: whilst Sandbox orgs can be selected, once they are refreshed the change in Salesforce org id will stop the job from working.).
Add a name for your monitoring job.
If no notification address exists for Apex error emails we recommend entering an email address recipient. You can enter an address at another time if you wish.
Click on
Finish setup.
To set up error monitoring specifically, Gearset will perform a deployment to adjust the notification settings required in the org for monitoring the inbox address which is automatically generated by Gearset. (Note: the length of time a deployment can take is dependent on when Salesforce begins the deployment so times can vary).
The deployment will update two settings in your org:
Under the
Apex exception emailit will add a Gearset generated email inbox to theExternal Email Addresses field.Change the existing
User Who Last Modified the Process or Flowdefault value to theApex Exception Email Recipientsoption underProcess Automation Settings.
The monitoring for Salesforce org limit monitoring requires no additional setup processes as it uses the REST API to retrieve information about current org limits.
Note: if you have a change monitoring job set up for your org or compare your org with the Apex email notifications or Settings metadata types included you will see the specific items for these types indicated as changed items.