Gearset has enabled a change to all your current and future standard backup jobs. This change is designed to more intelligently back up new objects, to prevent your backup job from automatically including new objects that utilise large numbers of API credits and are not business-critical for the vast majority of users.

Previously, when you add new objects to your org (or Salesforce creates new standard objects), we will automatically include these new objects in your backup job if you have the New objects setting enabled in your standard backup job (as on the screenshot below).
​

We will now only add new objects to your backup job if we class them as 'recommended objects'. This will appear in the user interface as below.

This will not affect any objects which are already backed up in your org - instead, it will only affect new objects added to your org going forward.

In future, if you need to back up any newly added objects which we don't recommend for backup, you can still include these in your backup by editing your object filter and ticking these objects in the list of objects manually.

'Recommended objects' cover the majority of Salesforce standard and custom objects, and has been curated by Gearset's engineers to include the vast majority of objects required for business-critical functions. 'Not recommended objects' include associated objects (including Feed, History and Share objects), 'debug' objects (such as Log, Metric, and Usage), and a few others.

'Not recommended objects' encapsulate objects which cannot be restored to your org, or experience large amounts of churn. Their inclusion can significantly increase the time taken for your backup to complete and use more API credits on objects that aren't useful to you. It can also cause noise in your backup due to these objects changing very frequently, potentially masking the changes your really care about.