Recommended async data cleanup

The Async processes generate large amounts of data, such as the data associated with queues, actions requests, and triggers. This data is meant to be transient, however, so you must perform regular purges. This reduces the storage space needed for data and makes troubleshooting easier.

For example, if you have a recurring schedule that starts an action group that is reused each time it runs, then any action invoked in the background from this also joins the group. If you do not clean these up, triggers build up and related action group member requests build up and just keep growing. Any time you need to glean information from the action group, there is an increasing number records to read.

To reduce the amount of async data on the system, turn off async history if not needed. To save history, purge it periodically.

For purging, use any schedulable purge actions that are available on the Recurring Requests tab of the Async Setup page. These include a finished trigger purge as well as ones that purge async data and many other types of data. Alternatively, there are different purge actions available on the individual forms for triggers, action requests, and queues. For example, the Requests form has an action to purge orphaned requests.