Apache Airflow
App · 15 actions
Run your Airflow pipelines: trigger DAG runs with a conf, follow and wait for them, re-run failed tasks, pause DAGs, read task logs, set Variables, and start a workflow when a DAG run fails or succeeds or a DAG file stops loading.
Actions
| Action | What it does |
|---|---|
| Clear DAG run | Run a DAG run's failed tasks again (or every task, or the ones you name), as clearing them in Airflow does. |
| Delete Variable | Delete an Airflow Variable. |
| Get DAG | Get a DAG: whether it's paused, its schedule and next run, its params (what its conf takes) and its newest run. |
| Get DAG run | Get a DAG run's state, conf and times, with each of its tasks' state and which failed. |
| Get task log | Get the log of a task in a DAG run, of its latest try or the one you choose, with the error it ended on. |
| Get Variable | Get an Airflow Variable's value, as text. |
| List DAG runs | List the runs of one DAG, or of every DAG, newest first, by state and since when. |
| List DAGs | List DAGs by ID, with whether each is paused, its schedule and its tags. |
| List import errors | List the DAG files Airflow can't load, newest first, with the error each fails on. |
| Mark DAG run | Mark a DAG run as succeeded or failed, with a note saying why, as Airflow's Mark run as button does. |
| Pause DAG | Pause a DAG, so no new runs start, by its schedule or by a trigger, until it's unpaused. |
| Set Variable | Set an Airflow Variable that DAGs read, such as a date to load from or a list of recipients, making it if there's none. |
| Trigger DAG run | Start a run of a DAG now, with a conf for it to read, as Airflow's Trigger button does. |
| Unpause DAG | Unpause a DAG, so its schedule runs it again and runs waiting in the queue start. |
| Wait for DAG run | Wait until a DAG run succeeds or fails, up to 15 minutes, then get it with each task's state. |
Clear DAG run
Run a DAG run's failed tasks again (or every task, or the ones you name), as clearing them in Airflow does. The run goes back to queued.
Inputs
- DAG
dag_idtextRequired - The DAG: pick one, or type its ID as Airflow lists it.
- DAG run
dag_run_idtextRequired - The run's ID, such as manual__2026-01-31T09:00:00+00:00: pick a recent run, or use the dag_run_id of an earlier step.
- Only failed tasks
only_failedtrue/false - Clear only the tasks that failed. Turn off to run every task again.Default:
true. - Tasks
task_idslist - Only these tasks, by ID. Leave empty for every task.
Outputs
cleared_countnumber- How many task instances were set to run again
cleared_taskslist- The IDs of the tasks set to run again
confobject- The conf it was triggered with
dag_idtext- The DAG's ID
dag_run_idtext- The run's ID, such as manual__2026-01-31T09:00:00+00:00
duration_secondsnumber- How long it took, in seconds; 0 until it finishes
end_datetext- When it finished (ISO 8601); empty until it does
finishedtrue/false- Whether it has succeeded or failed
linktext- A link to the run in Airflow
logical_datetext- Its logical date (ISO 8601); empty for a run triggered now
notetext- Its note; empty if none
queued_attext- When it was queued (ISO 8601)
run_aftertext- When it was due to run (ISO 8601)
run_typetext- How it started: manual, scheduled, backfill or asset_triggered
start_datetext- When it started (ISO 8601); empty until it does
statetext- queued, running, success or failed
triggered_bytext- Who or what triggered it
Example output
{
"cleared_count": 1,
"cleared_tasks": [
"load_orders"
],
"conf": {
"date": "2026-01-30"
},
"dag_id": "daily_sales_report",
"dag_run_id": "manual__2026-01-31T09:00:00+00:00",
"duration_seconds": 0.0,
"end_date": "",
"finished": false,
"link": "https://airflow.example.com/dags/daily_sales_report/runs/manual__2026-01-31T09%3A00%3A00%2B00%3A00",
"logical_date": "",
"note": "Started from Lodol",
"queued_at": "2026-01-31T09:00:00Z",
"run_after": "2026-01-31T09:00:00Z",
"run_type": "manual",
"start_date": "2026-01-31T09:00:04Z",
"state": "queued",
"triggered_by": "admin"
}Delete Variable
Delete an Airflow Variable. One that isn't there is left as it is.
Inputs
- Key
keytextRequired - The Variable's key, as Airflow lists it under Admin > Variables.
Outputs
deletedtrue/false- Whether it was deleted; false if there was none
keytext- The Variable's key
Example output
{
"deleted": true,
"key": "sales_report_recipients"
}Get DAG
Get a DAG: whether it's paused, its schedule and next run, its params (what its conf takes) and its newest run.
Inputs
- DAG
dag_idtextRequired - The DAG: pick one, or type its ID as Airflow lists it.
Outputs
active_runsnumber- How many of its runs are queued or running
dag_idtext- The DAG's ID
descriptiontext- Its description; empty if none
display_nametext- The name Airflow shows for it
doctext- Its documentation, in Markdown; empty if none
filetext- The file it's defined in
has_import_errorstrue/false- Whether its file fails to load
is_pausedtrue/false- Whether it's paused, so no new runs start
last_parsed_attext- When Airflow last read its file (ISO 8601)
last_run_attext- When its newest run was due (ISO 8601)
last_run_idtext- Its newest run's ID; empty if it never ran
last_run_statetext- Its newest run's state
linktext- A link to it in Airflow
next_run_attext- When its schedule runs it next (ISO 8601); empty if never
ownerslist- Its owners
paramsobject- Its params, what its conf takes, with their default values
scheduletext- When it runs, in Airflow's words, such as 'At 06:00'
tagslist- Its tags
Example output
{
"active_runs": 0,
"dag_id": "daily_sales_report",
"description": "Loads yesterday's orders and emails the report",
"display_name": "Daily sales report",
"doc": "Runs every morning at 06:00.",
"file": "sales/daily_sales_report.py",
"has_import_errors": false,
"is_paused": false,
"last_parsed_at": "2026-01-31T09:14:02Z",
"last_run_at": "2026-01-31T06:00:00Z",
"last_run_id": "scheduled__2026-01-31T06:00:00+00:00",
"last_run_state": "success",
"link": "https://airflow.example.com/dags/daily_sales_report",
"next_run_at": "2026-02-01T06:00:00Z",
"owners": [
"data-team"
],
"params": {
"date": null,
"send_email": true
},
"schedule": "At 06:00",
"tags": [
"finance",
"reports"
]
}Get DAG run
Get a DAG run's state, conf and times, with each of its tasks' state and which failed.
Inputs
- DAG
dag_idtextRequired - The DAG: pick one, or type its ID as Airflow lists it.
- DAG run
dag_run_idtextRequired - The run's ID, such as manual__2026-01-31T09:00:00+00:00: pick a recent run, or use the dag_run_id of an earlier step.
Outputs
confobject- The conf it was triggered with
dag_idtext- The DAG's ID
dag_run_idtext- The run's ID, such as manual__2026-01-31T09:00:00+00:00
duration_secondsnumber- How long it took, in seconds; 0 until it finishes
end_datetext- When it finished (ISO 8601); empty until it does
failed_taskslist- The IDs of the tasks that failed
finishedtrue/false- Whether it has succeeded or failed
linktext- A link to the run in Airflow
logical_datetext- Its logical date (ISO 8601); empty for a run triggered now
notetext- Its note; empty if none
queued_attext- When it was queued (ISO 8601)
run_aftertext- When it was due to run (ISO 8601)
run_typetext- How it started: manual, scheduled, backfill or asset_triggered
start_datetext- When it started (ISO 8601); empty until it does
statetext- queued, running, success or failed
task_countnumber- How many tasks the run has (up to 100 are listed)
taskslist- Each task of the run, in the order they started
triggered_bytext- Who or what triggered it
Example output
{
"conf": {
"date": "2026-01-30"
},
"dag_id": "daily_sales_report",
"dag_run_id": "manual__2026-01-31T09:00:00+00:00",
"duration_seconds": 217.0,
"end_date": "2026-01-31T09:03:41Z",
"failed_tasks": [
"load_orders"
],
"finished": true,
"link": "https://airflow.example.com/dags/daily_sales_report/runs/manual__2026-01-31T09%3A00%3A00%2B00%3A00",
"logical_date": "",
"note": "Started from Lodol",
"queued_at": "2026-01-31T09:00:00Z",
"run_after": "2026-01-31T09:00:00Z",
"run_type": "manual",
"start_date": "2026-01-31T09:00:04Z",
"state": "failed",
"task_count": 1,
"tasks": [
{
"duration_seconds": 215.0,
"end_date": "2026-01-31T09:03:40Z",
"link": "https://airflow.example.com/dags/daily_sales_report/runs/manual__2026-01-31T09%3A00%3A00%2B00%3A00/tasks/load_orders",
"map_index": -1,
"operator": "@task",
"start_date": "2026-01-31T09:00:05Z",
"state": "failed",
"task_id": "load_orders",
"try_number": 1
}
],
"triggered_by": "admin"
}Get task log
Get the log of a task in a DAG run, of its latest try or the one you choose, with the error it ended on.
Inputs
- DAG
dag_idtextRequired - The DAG: pick one, or type its ID as Airflow lists it.
- DAG run
dag_run_idtextRequired - The run's ID, such as manual__2026-01-31T09:00:00+00:00: pick a recent run, or use the dag_run_id of an earlier step.
- Task
task_idtextRequired - The task: pick one, or type its ID as the DAG names it.
- Try
try_numbernumber - Which try, from 1. Leave blank for the latest.At least 1.
- Map index
map_indexnumber - For a mapped task, which copy, from 0. Leave blank for a task that isn't mapped.At least 0.
Outputs
dag_idtext- The DAG's ID
dag_run_idtext- The run's ID
errortext- The error it ended on, such as KeyError: 'date'; empty if none
linktext- A link to the task in Airflow
logtext- The log, as text (its last 50,000 characters)
map_indexnumber- Its index among mapped copies; -1 if it isn't mapped
statetext- The task's state
task_idtext- The task's ID
truncatedtrue/false- Whether the start of the log was left out
try_numbernumber- Which try the log is of; 0 if it hasn't run
Example output
{
"dag_id": "daily_sales_report",
"dag_run_id": "manual__2026-01-31T09:00:00+00:00",
"error": "KeyError: 'region'",
"link": "https://airflow.example.com/dags/daily_sales_report/runs/manual__2026-01-31T09%3A00%3A00%2B00%3A00/tasks/load_orders",
"log": "2026-01-31T09:00:05Z INFO task: Loading orders for 2026-01-30\n2026-01-31T09:03:40Z ERROR task: Task failed with exception\nKeyError: 'region'",
"map_index": -1,
"state": "failed",
"task_id": "load_orders",
"truncated": false,
"try_number": 1
}Get Variable
Get an Airflow Variable's value, as text.
Inputs
- Key
keytextRequired - The Variable's key, as Airflow lists it under Admin > Variables.
Outputs
descriptiontext- Its description; empty if none
keytext- The Variable's key
valuetext- Its value, as text (JSON stays as written)
Example output
{
"description": "Who gets the daily sales report",
"key": "sales_report_recipients",
"value": "[\"finance@example.com\", \"ceo@example.com\"]"
}List DAG runs
List the runs of one DAG, or of every DAG, newest first, by state and since when.
Inputs
- DAG
dag_idtext - Only runs of this DAG. Leave blank for every DAG.
- State
statelist - Only runs in one of these states. Leave empty for all.One or more of:
queued,running,success,failed. - Since
sincedate and time - Only runs due to start at or after this time.
- How many
limitnumber - The most to list, 1 to 100. Defaults to 25.From 1 to 100.
Outputs
countnumber- How many are listed
dag_runslist- The runs, newest first
totalnumber- How many match in all
Example output
{
"count": 1,
"dag_runs": [
{
"conf": {
"date": "2026-01-30"
},
"dag_id": "daily_sales_report",
"dag_run_id": "manual__2026-01-31T09:00:00+00:00",
"duration_seconds": 217.0,
"end_date": "2026-01-31T09:03:41Z",
"finished": true,
"link": "https://airflow.example.com/dags/daily_sales_report/runs/manual__2026-01-31T09%3A00%3A00%2B00%3A00",
"logical_date": "",
"note": "Started from Lodol",
"queued_at": "2026-01-31T09:00:00Z",
"run_after": "2026-01-31T09:00:00Z",
"run_type": "manual",
"start_date": "2026-01-31T09:00:04Z",
"state": "failed",
"triggered_by": "admin"
}
],
"total": 1
}List DAGs
List DAGs by ID, with whether each is paused, its schedule and its tags.
Inputs
- ID contains
searchtext - Only DAGs whose ID has these letters, such as sales.
- Tags
tagslist - Only DAGs with any of these tags.
- Paused
pausedtext - Every DAG, only active ones or only paused ones.One of:
any,active,paused. Default:any. - How many
limitnumber - The most to list, 1 to 100. Defaults to 25.From 1 to 100.
Outputs
countnumber- How many are listed
dagslist- The DAGs, by ID
totalnumber- How many match in all
Example output
{
"count": 1,
"dags": [
{
"dag_id": "daily_sales_report",
"description": "Loads yesterday's orders and emails the report",
"display_name": "Daily sales report",
"file": "sales/daily_sales_report.py",
"has_import_errors": false,
"is_paused": false,
"last_parsed_at": "2026-01-31T09:14:02Z",
"link": "https://airflow.example.com/dags/daily_sales_report",
"next_run_at": "2026-02-01T06:00:00Z",
"owners": [
"data-team"
],
"schedule": "At 06:00",
"tags": [
"finance",
"reports"
]
}
],
"total": 1
}List import errors
List the DAG files Airflow can't load, newest first, with the error each fails on. A DAG whose file fails doesn't run.
Inputs
- How many
limitnumber - The most to list, 1 to 100. Defaults to 25.From 1 to 100.
Outputs
countnumber- How many are listed
import_errorslist- The import errors, newest first
totalnumber- How many there are in all
Example output
{
"count": 1,
"import_errors": [
{
"bundle": "dags-folder",
"error": "ModuleNotFoundError: No module named 'pandas_gbq'",
"filename": "sales/weekly_rollup.py",
"id": 12,
"stack_trace": "Traceback (most recent call last):\n File \"/opt/airflow/dags/sales/weekly_rollup.py\", line 4, in <module>\n import pandas_gbq\nModuleNotFoundError: No module named 'pandas_gbq'\n",
"timestamp": "2026-01-31T09:14:02Z"
}
],
"total": 1
}Mark DAG run
Mark a DAG run as succeeded or failed, with a note saying why, as Airflow's Mark run as button does. Tasks still going are stopped.
Inputs
- DAG
dag_idtextRequired - The DAG: pick one, or type its ID as Airflow lists it.
- DAG run
dag_run_idtextRequired - The run's ID, such as manual__2026-01-31T09:00:00+00:00: pick a recent run, or use the dag_run_id of an earlier step.
- Mark as
statetextRequired - Whether the run succeeded or failed.One of:
success,failed. - Note
notetext - A note Airflow shows on the run, such as why it was started.
Outputs
confobject- The conf it was triggered with
dag_idtext- The DAG's ID
dag_run_idtext- The run's ID, such as manual__2026-01-31T09:00:00+00:00
duration_secondsnumber- How long it took, in seconds; 0 until it finishes
end_datetext- When it finished (ISO 8601); empty until it does
finishedtrue/false- Whether it has succeeded or failed
linktext- A link to the run in Airflow
logical_datetext- Its logical date (ISO 8601); empty for a run triggered now
notetext- Its note; empty if none
queued_attext- When it was queued (ISO 8601)
run_aftertext- When it was due to run (ISO 8601)
run_typetext- How it started: manual, scheduled, backfill or asset_triggered
start_datetext- When it started (ISO 8601); empty until it does
statetext- queued, running, success or failed
triggered_bytext- Who or what triggered it
Example output
{
"conf": {
"date": "2026-01-30"
},
"dag_id": "daily_sales_report",
"dag_run_id": "manual__2026-01-31T09:00:00+00:00",
"duration_seconds": 217.0,
"end_date": "2026-01-31T09:03:41Z",
"finished": true,
"link": "https://airflow.example.com/dags/daily_sales_report/runs/manual__2026-01-31T09%3A00%3A00%2B00%3A00",
"logical_date": "",
"note": "Started from Lodol",
"queued_at": "2026-01-31T09:00:00Z",
"run_after": "2026-01-31T09:00:00Z",
"run_type": "manual",
"start_date": "2026-01-31T09:00:04Z",
"state": "failed",
"triggered_by": "admin"
}Pause DAG
Pause a DAG, so no new runs start, by its schedule or by a trigger, until it's unpaused. Runs going now carry on.
Inputs
- DAG
dag_idtextRequired - The DAG: pick one, or type its ID as Airflow lists it.
Outputs
changedtrue/false- Whether it changed; false if it was already so
dag_idtext- The DAG's ID
descriptiontext- Its description; empty if none
display_nametext- The name Airflow shows for it
filetext- The file it's defined in
has_import_errorstrue/false- Whether its file fails to load
is_pausedtrue/false- Whether it's paused, so no new runs start
last_parsed_attext- When Airflow last read its file (ISO 8601)
linktext- A link to it in Airflow
next_run_attext- When its schedule runs it next (ISO 8601); empty if never
ownerslist- Its owners
scheduletext- When it runs, in Airflow's words, such as 'At 06:00'
tagslist- Its tags
Example output
{
"changed": true,
"dag_id": "daily_sales_report",
"description": "Loads yesterday's orders and emails the report",
"display_name": "Daily sales report",
"file": "sales/daily_sales_report.py",
"has_import_errors": false,
"is_paused": true,
"last_parsed_at": "2026-01-31T09:14:02Z",
"link": "https://airflow.example.com/dags/daily_sales_report",
"next_run_at": "2026-02-01T06:00:00Z",
"owners": [
"data-team"
],
"schedule": "At 06:00",
"tags": [
"finance",
"reports"
]
}Set Variable
Set an Airflow Variable that DAGs read, such as a date to load from or a list of recipients, making it if there's none.
Inputs
- Key
keytextRequired - The Variable's key, as Airflow lists it under Admin > Variables.
- Value
valuetextRequired - What to set it to. A list or object is saved as JSON.
- Description
descriptiontext - What it's for. Leave blank to keep the one it has.
Outputs
createdtrue/false- Whether it was made, there being none with that key
descriptiontext- Its description; empty if none
keytext- The Variable's key
valuetext- Its value, as text (JSON stays as written)
Example output
{
"created": false,
"description": "Who gets the daily sales report",
"key": "sales_report_recipients",
"value": "[\"finance@example.com\", \"ceo@example.com\"]"
}Trigger DAG run
Start a run of a DAG now, with a conf for it to read, as Airflow's Trigger button does. It doesn't wait for the run: follow it with Wait for DAG run or Get DAG run.
Inputs
- DAG
dag_idtextRequired - The DAG: pick one, or type its ID as Airflow lists it.
- Conf
confobject - What the run gets as its conf (its params), such as {"date": "2026-01-31"}. Leave blank for the DAG's defaults.
- Run ID
dag_run_idtext - An ID for the run, unique in the DAG. Leave blank for Airflow's own, such as manual__2026-01-31T09:00:00+00:00.
- Note
notetext - A note Airflow shows on the run, such as why it was started.
Outputs
confobject- The conf it was triggered with
dag_idtext- The DAG's ID
dag_is_pausedtrue/false- Whether the DAG is paused, so the run waits until it isn't
dag_run_idtext- The run's ID, such as manual__2026-01-31T09:00:00+00:00
duration_secondsnumber- How long it took, in seconds; 0 until it finishes
end_datetext- When it finished (ISO 8601); empty until it does
finishedtrue/false- Whether it has succeeded or failed
linktext- A link to the run in Airflow
logical_datetext- Its logical date (ISO 8601); empty for a run triggered now
notetext- Its note; empty if none
queued_attext- When it was queued (ISO 8601)
run_aftertext- When it was due to run (ISO 8601)
run_typetext- How it started: manual, scheduled, backfill or asset_triggered
start_datetext- When it started (ISO 8601); empty until it does
statetext- queued, running, success or failed
triggered_bytext- Who or what triggered it
Example output
{
"conf": {
"date": "2026-01-30"
},
"dag_id": "daily_sales_report",
"dag_is_paused": false,
"dag_run_id": "manual__2026-01-31T09:00:00+00:00",
"duration_seconds": 0.0,
"end_date": "",
"finished": false,
"link": "https://airflow.example.com/dags/daily_sales_report/runs/manual__2026-01-31T09%3A00%3A00%2B00%3A00",
"logical_date": "",
"note": "Started from Lodol",
"queued_at": "2026-01-31T09:00:00Z",
"run_after": "2026-01-31T09:00:00Z",
"run_type": "manual",
"start_date": "",
"state": "queued",
"triggered_by": "admin"
}Unpause DAG
Unpause a DAG, so its schedule runs it again and runs waiting in the queue start.
Inputs
- DAG
dag_idtextRequired - The DAG: pick one, or type its ID as Airflow lists it.
Outputs
changedtrue/false- Whether it changed; false if it was already so
dag_idtext- The DAG's ID
descriptiontext- Its description; empty if none
display_nametext- The name Airflow shows for it
filetext- The file it's defined in
has_import_errorstrue/false- Whether its file fails to load
is_pausedtrue/false- Whether it's paused, so no new runs start
last_parsed_attext- When Airflow last read its file (ISO 8601)
linktext- A link to it in Airflow
next_run_attext- When its schedule runs it next (ISO 8601); empty if never
ownerslist- Its owners
scheduletext- When it runs, in Airflow's words, such as 'At 06:00'
tagslist- Its tags
Example output
{
"changed": true,
"dag_id": "daily_sales_report",
"description": "Loads yesterday's orders and emails the report",
"display_name": "Daily sales report",
"file": "sales/daily_sales_report.py",
"has_import_errors": false,
"is_paused": false,
"last_parsed_at": "2026-01-31T09:14:02Z",
"link": "https://airflow.example.com/dags/daily_sales_report",
"next_run_at": "2026-02-01T06:00:00Z",
"owners": [
"data-team"
],
"schedule": "At 06:00",
"tags": [
"finance",
"reports"
]
}Wait for DAG run
Wait until a DAG run succeeds or fails, up to 15 minutes, then get it with each task's state. A run still going when the wait is up carries on in Airflow.
Inputs
- DAG
dag_idtextRequired - The DAG: pick one, or type its ID as Airflow lists it.
- DAG run
dag_run_idtextRequired - The run's ID, such as manual__2026-01-31T09:00:00+00:00: pick a recent run, or use the dag_run_id of an earlier step.
- Wait up to (minutes)
max_wait_minutesnumber - How long to wait, 1 to 15 minutes. Defaults to 5.From 1 to 15.
Outputs
confobject- The conf it was triggered with
dag_idtext- The DAG's ID
dag_run_idtext- The run's ID, such as manual__2026-01-31T09:00:00+00:00
duration_secondsnumber- How long it took, in seconds; 0 until it finishes
end_datetext- When it finished (ISO 8601); empty until it does
failed_taskslist- The IDs of the tasks that failed
finishedtrue/false- Whether it has succeeded or failed
linktext- A link to the run in Airflow
logical_datetext- Its logical date (ISO 8601); empty for a run triggered now
notetext- Its note; empty if none
queued_attext- When it was queued (ISO 8601)
run_aftertext- When it was due to run (ISO 8601)
run_typetext- How it started: manual, scheduled, backfill or asset_triggered
start_datetext- When it started (ISO 8601); empty until it does
statetext- queued, running, success or failed
task_countnumber- How many tasks the run has (up to 100 are listed)
taskslist- Each task of the run, in the order they started
timed_outtrue/false- Whether the wait ran out before the run finished
triggered_bytext- Who or what triggered it
waited_secondsnumber- How long the step waited, in seconds
Example output
{
"conf": {
"date": "2026-01-30"
},
"dag_id": "daily_sales_report",
"dag_run_id": "manual__2026-01-31T09:00:00+00:00",
"duration_seconds": 217.0,
"end_date": "2026-01-31T09:03:41Z",
"failed_tasks": [
"load_orders"
],
"finished": true,
"link": "https://airflow.example.com/dags/daily_sales_report/runs/manual__2026-01-31T09%3A00%3A00%2B00%3A00",
"logical_date": "",
"note": "Started from Lodol",
"queued_at": "2026-01-31T09:00:00Z",
"run_after": "2026-01-31T09:00:00Z",
"run_type": "manual",
"start_date": "2026-01-31T09:00:04Z",
"state": "failed",
"task_count": 1,
"tasks": [
{
"duration_seconds": 215.0,
"end_date": "2026-01-31T09:03:40Z",
"link": "https://airflow.example.com/dags/daily_sales_report/runs/manual__2026-01-31T09%3A00%3A00%2B00%3A00/tasks/load_orders",
"map_index": -1,
"operator": "@task",
"start_date": "2026-01-31T09:00:05Z",
"state": "failed",
"task_id": "load_orders",
"try_number": 1
}
],
"timed_out": false,
"triggered_by": "admin",
"waited_seconds": 210
}