Error reference

app_unavailable

HTTP status

409 Conflict

Returned by

Automations

What it means

An automation can't be turned on because an app it needs is off, uninstalled, suspended, lacks access, or its actions keep failing. app, app_name and reason say which app and why.

Typical causes

• Turning on an automation (POST /v1/automations/{id}/enable) whose trigger or an action belongs to an unavailable app. reason is one of app_disabled, app_uninstalled, app_suspended, app_missing_scope, app_trigger_removed, app_action_removed, app_failing.

How to fix it

• Make the app available first (turn it on, reinstall it, approve its access, or press Try again after its actions failed). Automations Kweko paused for the app turn back on by themselves when it is back.

Message

English text, as sent with Accept-Language: en. With ru or uz the API sends the translation.

• The message depends on the situation and is built at run time.

Example response

HTTP/1.1 409 Conflict
Content-Type: application/json; charset=utf-8
X-Request-Id: req_4f2a9c1e0b7d3a55

{
  "error": {
    "code": "app_unavailable",
    "message": "…",
    "request_id": "req_4f2a9c1e0b7d3a55",
    "docs_url": "https://docs.kweko.uz/errors/app_unavailable",
    "app": "stock-sync",
    "app_name": "Stock Sync",
    "reason": "app_disabled"
  }
}

Related

• app_disabled

All error codes · The error format