Automation History, Failures, and Stop-on-Failure Settings

Written By Usama Ejaz

Last updated 13 days ago

Overview

Automation history helps you review recent automation activity, successful actions, skipped executions, and errors.

Where to find history

  1. Go to Automate.

  2. Open the automation.

  3. Open History or Show Log, depending on the editor view.

What history can show

  • When an automation was created, updated, enabled, disabled, or deleted.

  • When actions were executed.

  • Errors returned by actions or invalid settings.

  • Skipped executions, such as when a monthly execution limit is reached.

  • The message Monthly automation execution limit reached. when the workspace has used its monthly automation executions.

Stop on failure

If stop on failure is enabled, SocialBu may deactivate an automation when an action fails. If stop on failure is disabled, SocialBu logs the error and keeps the automation available instead of deactivating it because of that failure.

Use this setting carefully. Keeping an automation active after failures can be useful for temporary API issues, but repeated failures should still be fixed from the history details.

Why an automation may stop

  • The connected account is no longer available.

  • An RSS feed becomes invalid or unreachable repeatedly.

  • An action fails and the automation is configured to stop on failure.

  • The account or team reaches an automation resource limit.

What to do next

Review the history, fix the account, RSS feed, action, or request body, then switch the automation back to Active.

Need further assistance?

If you need help, email us at support@socialbu.com.