Run History — Full Visibility Into Every Workflow
See every automation run as it happens—status, duration, and actions executed—so your team verifies that workflows fired, pinpoints failures fast, and keeps an execution record auditors can trust.
What Is Run History?
Run History is the execution log for each SmartSuite automation—a real-time record of past runs used to monitor activity and debug failures. It helps Administrators and Solution Managers confirm that workflows fired, diagnose errors from specific run details, and track action consumption against plan quotas—turning automation from a black box into an accountable system. Run History is available on every plan, with retention windows that scale by tier.
Execution Log
Track Every Run with Status, Duration, and Actions Executed
Open the History view inside any automation and every run is listed—start time, success or error status, duration, and the number of actions executed. A scheduled sweep that ran overnight, a form-triggered workflow that fired at 2 p.m.—each leaves a timestamped entry.
That per-run action count also shows exactly how a multi-step automation consumes your plan's monthly quota.
Error Diagnosis
Diagnose Failures From Specific Error Descriptions
Error entries include descriptions that point to the cause—a deleted field leaving an input empty, a server timeout, a failure returned by an external service like Slack or Twilio, invalid data such as a missing record ID or phone number, or an unavailable select option.
Administrators and Solution Managers also receive email and in-app notifications the moment an automation errors, so failures surface before they become missed SLAs or skipped control tests.
Retention & Access
Retain Execution Records on an Enterprise Timeline
Run logs are retained for one year on Team, two years on Professional, and three years on Enterprise and Signature—long enough to answer "did this control automation actually run last quarter?" with a timestamped record rather than a recollection.
Only Administrators and Solution Managers can view the full run logs across the Solutions they manage, keeping execution data with accountable owners.
Run History
Automated workflows only earn trust when their execution is provable. Run History gives GRC teams the evidence layer for their automations—what ran, when, how long it took, and why anything failed.
When recurring control tests are automated, Run History shows each scheduled execution with its timestamp and status—an execution record that supports audit-ready documentation of the process.
An attestation-reminder automation errors after a field is renamed. The error notification and run detail pinpoint the cause the same day—before a reporting cycle passes with no reminders sent.
Plan-based retention keeps run logs for years, so when an auditor asks whether last year's access-review automation fired each quarter, the answer is a timestamped record—not a recollection.
When automated evidence notifications to Slack or email stop arriving, the run detail shows the external-service error—distinguishing an expired connection from a workflow bug and cutting time to resolution.
Pair Run History with Automations to audit how many actions your busiest control-testing and escalation workflows consume—then tune loops and branches before monthly run quotas are hit.
Automated workflows only earn trust when their execution is provable. Run History gives GRC teams the evidence layer for their automations—what ran, when, how long it took, and why anything failed.
Run History is the execution log for each automation—a real-time record of past runs accessed from the History button inside an automation. It's used to monitor activity, verify workflows fired, and debug failures.
Each entry shows the run's start time, status (success or error), duration, and the number of actions executed. Error entries add a description of what went wrong.
Retention scales by plan: one year on Team, two years on Professional, and three years on Enterprise and Signature.
Error entries describe the specific cause—deleted fields, server timeouts, external-service failures from tools like Slack or Twilio, invalid data such as missing record IDs, or unavailable select options—so you fix the actual problem instead of guessing.
Administrators and Solution Managers are the only roles that can view the full run logs for automations across the Solutions they manage. They also receive email and in-app notifications when an automation errors.
Every automated run leaves a timestamped entry with its status and actions executed, retained on a multi-year window on upper tiers. That execution record helps GRC and IT teams document that automated steps in governed processes actually ran.
Trust Your Automations—And Prove They Ran
Put your workflows on autopilot with an execution record behind every run—monitored, debuggable, and retained.