ClickSabi Pro
Troubleshooting
Automation problems
Rules that do not fire, skip, or fail.
1 min readLast updated
A rule never fires
Check that it is enabled and that its trigger has actually occurred. Time-based triggers depend on the scheduler; the overview shows a banner when scheduled runs are off or paused.
A run was skipped
Each run records the plain-language reason it did not act. A skip is usually a condition that was not met, not an error.
A run failed
Fix the cause shown on the run, then re-enable the rule. Failed runs do not retry silently.
Nothing runs at all
A read-only workspace preserves automations but stops them executing until billing is restored.
Related articles
- AutomationsRun history and failuresSee what ran, what was skipped, and what needs attention.
- AutomationsTriggers and actionsWhat can start an automation and what it can do.
- Getting StartedWho can open the Pro workspaceThe access requirements, and what changes when billing lapses.
- TroubleshootingAccess and workspace problemsSign-in, workspace access and invitation issues.
Didn't find what you were looking for?
Get in touch with the ClickSabi team or send feedback about the Help Center.
Prefer email? support@mail.clicksabi.com