Error code generation
In case the error is aUser Error and there’s no matching error code, maintenance agent will suggest a new error code. You can approve these error codes in our platform.
Once approved, the error code is returned in future runs in the execution.failed webhook.
Error‑classification matrix
| Category | Sub‑category | Description |
|---|---|---|
User Error | PAGE_NOT_FOUND | URL returns 404; usually bad ID/slug |
AUTHENTICATION_ERROR | Wrong or expired credentials, unexpected 2FA, captcha, password reset | |
INCORRECT_FORM_INPUTS | Provided value empty, invalid, or fails validation | |
PASSWORD_UPDATE_REQUIRED | Site forces password change before further access | |
ADDITIONAL_USER_INPUT_REQUIRED | Unexpected gating modal that truly blocks progress | |
MULTIPLE_MATCHING_RESULTS_FOUND | Ambiguous search results require human or AI disambiguation | |
ACTION_BLOCKED_BY_PLATFORM | Platform rejects duplicate or forbidden action | |
Workflow Error | ACTION_PERFORMED_TOO_EARLY | Clicked before element was fully loaded |
UNEXPECTED_POPUP | Optional modal (survey, promo, cookie banner) appeared | |
UNEXPECTED_UI_STATE | Layout/state differs (already logged in, collapsed sidebar) | |
XPATH_INCORRECT | Selector matches 0 or >1 elements | |
External Error | SERVICE_UNAVAILABLE | Upstream system down or non‑responsive |
PAGE_STILL_LOADING | The workflow ended in a loading state | |
ACCOUNT_LOGGED_OUT | The website logged out the account unexpectedly |
Recovery playbook
| Classification | Action |
|---|---|
| User Error | Surface a dashboard alert + notification; ask the user to correct data or credentials. |
| Workflow Error | Auto‑patch the graph: update selectors or insert waits. |
| External Error | Schedule exponential back‑off retries; no graph change. |
execution.requeued until the run is started again.
Service Unavailable Recovery
When a workflow encounters an external service unavailability (503 errors, timeouts, maintenance pages), the Maintenance Agent can automatically retry the workflow using exponential backoff. Retry Schedule The delay between retries follows the formula:10 minutes × 2^n (where n is the retry attempt number, starting at 0), with ±20% jitter to prevent thundering herd issues.
| Retry | Approximate Delay |
|---|---|
| 1 | ~10 minutes |
| 2 | ~20 minutes |
| 3 | ~40 minutes |
| 4 | ~1.3 hours |
| 5 | ~2.7 hours |
| 6 | ~5.3 hours |
| 7 | ~10.7 hours |
| 8 | ~21 hours |
| 9 | ~1.8 days |
| 10 | ~3.5 days |
execution.failed webhook is sent to your registered webhook URL. This allows you to:
- Alert your team via PagerDuty, Slack, or other alerting systems
- Queue the failure for manual review
- Trigger alternative fallback logic on your end