automation_replay_not_allowed
The run exists and is yours, but relaunching it does not apply: it has not finished yet, it finished well and its effect already happened, its outcome would take exactly the same branch again, or no outcome was recorded for it.
| Code | Type | HTTP | Category |
|---|---|---|---|
automation_replay_not_allowed | invalid_request_error | 422 | Automations |
Cause
The run exists and is yours, but relaunching it does not apply: it has not finished yet, it finished well and its effect already happened, its outcome would take exactly the same branch again, or no outcome was recorded for it.
What to do
Read the message together with status: for work still in flight, wait; for work that ended well, there is nothing to relaunch; for an outcome that would repeat itself, fix its cause and let a new event fire the rule.
Related
All Automations error codes
Causes and actions for errors in this category.
Error codes by category
Find an error by the category that emits it.
Full reference table
All codes, HTTP statuses, types and descriptions in one reference.
Error model
Interpret the error envelope and handle errors by code.