Skip to main content
By default, task execution is synchronous — the API call waits for the task to complete before returning results. For long-running tasks, you can use asynchronous execution to start the task and check results later.

Running tasks asynchronously

When you set async: true, the API returns immediately with a confirmation that the task has started. You can then poll for execution results using the task execution history endpoint.

Checking execution results

After starting an async task, you can check its execution status and results by querying the task’s execution history endpoint:
Example response:
Async task executions have a maximum duration of 3 hours. Tasks that exceed this limit will be automatically cancelled.Note: Tasks must be deployed (not just in draft) to appear in the execution results list.

Polling for results

For async tasks, you can implement polling to wait for completion: