Aller au contenu
Runner AI
Aide et référence
Français
Esc
↑↓naviguer↵ouvrir⌘Japerçu

Run failed

Automation runs, triggers, and management. Exact Runner messages, recovery steps, and checks for the completed result.

For an automation list, event catalog, run detail, or health-check load failure, retry that view. When Real test is off, follow the reason shown on its choice, such as publishing your store or retrying the health check; Safe test still works. An automation you test with inputs keeps Real test when its health check fails; only Skip waits is off until the check loads.

For a failed run, inspect the failed step and completed outputs. Retry only when that step offers a safe retry: earlier steps may already have sent messages or changed external data. A failed stop, pause, resume, or trigger removal requires inspecting current run/trigger state before assuming it took effect.

For batch operations with partial success, retry remaining/failed items only. For failed create, duplicate, rename, pin, delete, or deploy, inspect the automation list or active deployment before repeating. Success means the intended saved/deployed state or trigger status is shown; a run is recovered only after its required steps and external results succeed. Escalate with the automation, run, and failed step.

Messages covered:

  • Couldn’t pause {triggers}.
  • Paused {triggers}. {failed} could not be paused.
  • We lost track of this project. Refresh to continue.
  • We couldn’t delete the selected automations. Try again.
  • None of the {count} automations could be deleted. They remain selected so you can try again.
  • Deleted {deleted} of {total} automations. {failed} remain selected so you can try again.
  • We couldn’t delete this automation. Try again.
  • We couldn’t duplicate this automation. Try again.
  • We couldn’t export your selection. Try again.
  • Exported {exported} of {total} automations. Try the failed items again.
  • We couldn’t update the pinned state. Try again.
  • We couldn’t rename this automation. Try again.
  • Your automations are still safe. Check your connection and try loading the list again.
  • We couldn’t load automations
  • We couldn’t create the automation. Try again.
  • Couldn’t deploy the automation. Try again.
  • Recent events could not be loaded.
  • Unable to load run details
  • Upload failed
  • Save or discard these changes before duplicating the node.
  • The selected run is still available. Check your connection and try again.
  • Run failed
  • Completed steps and their outputs remain available below. Retry only when the failed step offers a safe retry.
  • Select Test, then Run safe test, to create the first entry. Test is available once this automation has an action, logic, code, or data step.
  • Your run history is still safe. Check your connection and try again.
  • Couldn’t load runs
  • Couldn’t prepare the change preview.
  • Automation version is unavailable. Refresh before deploying.
  • Automation not found
  • Real test is unavailable right now.
  • Your organization’s event catalog is unavailable. Retry before choosing an event trigger.
  • Couldn’t load events
  • Failed to load automations
  • Couldn’t pause the trigger.
  • Couldn’t remove the trigger.
  • Couldn’t resume the trigger.
  • Retry failed
  • Retry failed: {status}
  • A required store link could not be built from this event.
  • Automation health couldn’t be loaded
  • Real test stays off until it works again.
  • Real test still works, but Skip waits stays off until health loads again.
  • Could not stop this run. Try again.

For repeated failures, see what to send Runner.

Dernière mise à jour le 25 octobre 2026

Cette page vous a-t-elle été utile ?