Every automation-driven change on a record now includes a direct link to the specific automation run that made it, embedded in the record's Activity History. Change managers investigating an unexpected update, GRC auditors tracing per-record data changes to their source, and anyone debugging an automation outcome can now hop straight from the affected record to the run that touched it, instead of scrolling through the automation's run history one-by-one.
Key Highlights
- Embedded Run Links in Activity History: Every automation-driven change on a record now includes a clickable link on that record's Activity History entry, pointing directly to the run in the automation's own History that made the change.
- Bulk-Trigger Friendly: When a bulk trigger updates dozens or hundreds of records in a single run, the record-side link jumps to the specific run/record combination, so investigating a single unexpected outcome doesn't require a needle-in-haystack hunt through the run list.
- Preserves Full Run Context: Following the link opens the automation run's details view with the trigger, input data, every step's outcome, error messages, and downstream side effects visible for review.
- Applies to Every Change Type: Field updates, linked-record modifications, status changes, comment creation, any record-modifying automation step gets the same traceability.
- Standard Permissions Apply: The run link respects the same automation-viewer permissions on the containing solution; it doesn't grant visibility to anyone who couldn't reach the run through normal navigation.
How It Works
- Open the affected record and switch to its Activity History.
- Find the entry for the automation-driven change you want to investigate (each entry shows the automation name, the change made, and the timestamp).
- Click the run link on that Activity History entry; you land on that specific run's details view inside the automation's own History.
- Review the trigger record, input data, and every step's outcome to understand exactly what the automation did on this execution.
- Use this to diagnose an unexpected outcome on one specific record without having to walk through every run of a bulk-triggered automation.
Use this whenever a record ends up in an unexpected state and you need to trace exactly which automation execution caused it.