Rerunning Automation Workflows
When an automation fails, you don't have to start from scratch. Glacis lets you rerun the automation — either from the beginning or from a specific step — so you can recover without losing the work that already succeeded.
When to use Rerun
The Rerun button appears on any automation run that has finished in a failed, skipped, or cancelled state. Use it when:
An automation failed partway through and you've fixed the underlying issue (e.g., corrected a missing field, updated a configuration).
You've published a newer version of the workflow and want to run the failed data through the updated logic.
An automation was skipped or cancelled but you now want it to run.
How to rerun an automation
Open the workflow and go to the History tab.
Select the failed run you want to retry.
Click the Rerun button in the top-left corner of the run detail view.
A dialog opens with two choices:
Rerun from step
Pick which step to start from. Glacis defaults to the first failed step, so everything that succeeded before it is preserved and the run picks up where it left off.
You can also choose an earlier step if you want to re-process more of the automation.
On version
Pick which version of the workflow to run on. You'll see:
Origin — the version the original run used.
Current — the currently published version (if it's newer).
Latest — any other newer versions available.
Tip: If you've fixed a bug in your workflow and published a new version, select the newer version here. Glacis will run your data through the corrected logic instead of the original.
Only versions that contain the selected step are shown. If a step was removed in a newer version, that version won't appear as an option.
Confirm the rerun
Click Rerun to start the new run.
Glacis creates a fresh automation run. The original run is marked as cancelled and the new run begins processing. You'll be taken to the new run's detail view automatically.
Rerun lineage
When you view a rerun, Glacis shows a version chain in the run's metadata — linking back to the original run and forward to any subsequent reruns. This makes it easy to trace the full history of retries for a single piece of data.
For example: v3 → v5 → v5 means the original ran on version 3, was rerun on version 5, and rerun again on version 5.
Click any version in the chain to jump to that run.
Resolving a failed automation without rerunning
Sometimes a failed automation doesn't need to be rerun — the issue was handled manually or isn't relevant anymore. In that case, use the Resolve button instead.
Resolve appears next to the Rerun button on failed runs that are blocking the email automation queue. It marks the run as resolved (skipped) and unblocks any automations waiting behind it.
Click Resolve.
Enter a reason explaining why this run is being skipped.
Click Mark as Resolved.
Note: Resolve does not re-process the automation. If the automation was supposed to create something (like a record or a task), you'll need to handle that manually. See Why didn't my email trigger an automation? for more on unblocking email automation queues.
Need help?
If you have questions or run into issues, we're here to help:
Chat with us — use the support widget in the bottom-right corner of Glacis
Email — reach us at support@glacis.com
Related docs