This problem analyzer solves an issue with deploying Chatter feed tracking on objects.

What triggers this problem analyzer?

Deploying a change to the feed tracking on a custom object will trigger this analyzer.

What problem is it solving?

If feed tracking on an object is disabled in the target, deploying a change to the feed tracking will cause the deployment to fail with a message similar to:
The entity: <object> does not have history tracking enabled .

How does it work?

Gearset will prompt you to remove changes to feed tracking from your deployment. This will make the deployment more likely to succeed.

Did this answer your question?