Automate activity is recorded based on the condition and when certain metadata properties are changed or updated.
Activity that is based on the automation condition, such as Automation triggered and Automation recovered, is saved at the user level. This means you cannot see whether an automation triggered and executed for another user even when you created the automation. You can only see whether an automation triggered for you.
The activity timeline for all automations related to a user is displayed on the Overview page of the Automate application.

The activity timeline for a single automation is displayed under the History tab in the individual automation view.

Automate activity is visible only to the owner. However, you can enable shared events to make the activity visible to users other than the owner.
Shared events are only shown when the execution was performed, and the result of the execution cannot be viewed by users other than the owner.
You can enable shared events by navigating to the Automate edit page and selecting Summary > Security settings, then choosing User scoped, and turning on Generate shared history events.

When you enable shared events, you can switch between the Only my events and Shared events tabs on Automate's History tab.

Automation triggeredAutomation triggered is recorded when an automation condition is met or when a threshold condition changes status from false to true.
Automation recoveredAutomation recovered is recorded when a threshold condition changes status from true to false. Only object set threshold conditions can result in automation recovered activity.
Condition editedCondition edited is recorded when the automation condition is updated by any user.
SubscribedSubscribed is recorded when you subscribe to an automation. Activity from periods where you are not subscribed will not be recorded or displayed.
UnsubscribedUnsubscribed is recorded when you unsubscribe from an automation. Activity from periods where you are not subscribed will not be recorded or displayed.
Evaluation failedEvaluation failed is recorded when an automation fails to evaluate for any reason. Details about the failure can be viewed from the activity History view for that automation. Evaluation failed may also be shown in cases where the automation condition was successfully evaluated, but the notification or Actions effect failed.
PausedPaused is recorded when an automation is paused by any user or when an automation is automatically paused due to excessive activity. Pausing applies to the whole automation. Paused automations are not evaluated.
ResumedResumed is recorded when an automation stops being paused. Resuming applies to whole automation.
MutedMuted is recorded when an automation is muted by any user. Muting applies to all subscribers. Muted automation will still be evaluated, but no effects (e.g. notifications or Actions) will be triggered.
UnmutedUnmuted is recorded when an automation stops being muted. Muting applies to all subscribers, and automations will be automatically unmuted after the mute time period expires.
Historical activity for automations is retained for six months and permanently deleted after that time. If historical activity must be stored beyond this date, you can use Actions to store data in a long-lived object that is managed and controlled like any other user-created object in the Foundry Ontology.
When data is deleted, it is also removed from the automation activity History tab in the Automate application. You can find the History tab by first clicking on an automation to expand the overview panel, then clicking History.