Hi Smartsheet Community! π
I'd like to submit a feature request for an Automation Run History or Execution Log for all workflow types β specifically for Alert, Notification, Reminder, Copy Row, and Move Row automations.
π Current Limitation
Right now, Smartsheet only provides:
- A "Last Run" timestamp in Manage Automation Workflows (but no details on who received it)
- A dedicated log for Update Requests (which is great β we'd love this for other automation types too!)
- Activity Log β which tracks sheet edits and automation modifications, but does not show each time an automation was triggered or who received the notification
This makes it difficult to:
- Verify whether an alert or notification was successfully sent
- Audit which recipients received a specific automation
- Troubleshoot issues without contacting Smartsheet Support
- Determine why a Move Row or Change Cell Value automation did not execute as expected
β
Requested Feature
A dedicated Automation Run Log accessible per workflow, showing:
Field | Description |
|---|
Triggered Date/Time | When the automation fired |
|---|
Trigger Condition Met | What row/change triggered it |
|---|
Recipient(s) | Who received the alert/notification |
|---|
Delivery Status | Sent / Failed / Skipped |
|---|
Run Result | Success / Error with reason |
|---|
Ideally, this would be accessible from Manage Automation Workflows by clicking into a specific workflow β similar to how Bridge by Smartsheet provides step-by-step run logs.
π Use Case Examples
1. Alert & Notification Verification - In our team, we use automation to notify team leads and agents when a new evaluation or exception request is submitted. When a recipient reports not receiving a notification, we currently have no native way to verify whether the automation fired or who it was sent to β making troubleshooting very manual and time-consuming.
2. Move Row & Change Cell Value Troubleshooting - When a Move Row or Change Cell Value automation doesn't behave as expected, there is currently no way to determine:
- Whether the automation was triggered at all
- Whether the trigger condition was evaluated but not met
- Whether the action was attempted but failed silently
- What specific row, field, or value was involved at the time of execution
This leaves users guessing β checking trigger conditions, permission settings, and sheet structure manually β with no clear starting point for troubleshooting. A run log with a skip or failure reason would significantly reduce the time spent diagnosing these issues.
π Why This Matter
- Improves transparency and accountability for workflow-driven processes
- Reduces dependency on Smartsheet Support for basic troubleshooting
- Supports audit and compliance needs for teams using Smartsheet for operational tracking
- Gives users a clear starting point when automation doesn't fire or execute as expected
- Aligns Smartsheet automation capabilities with industry-standard workflow tools that include execution history
I believe this would be a valuable addition for many teams relying on automation for critical notifications and operational workflows. Would love to hear if others are experiencing the same gap! π