Skip to main content
A browser task is the smallest way to ask Infragrid to explore a site and return a result. Use it when the route through the site is not known in advance.
Public cloud browser tasks are read-only jobs, not directly connectable Playwright or CDP sessions. They use a clean, ephemeral browser without local cookies or signed-in sessions. Approval-requiring actions, credentials, payments, destructive controls, and external submissions fail closed. Use the desktop product for work that needs an existing local session or direct human control.

Start a task

Lifecycle

queued → running → completed, failed, or cancelled The create call returns as soon as the run is durably accepted. Poll GET /v1/runs/{run_id}, use an SDK wait helper, or recover the same run later by ID.

Task-writing guidance

  • State the desired outcome and important constraints.
  • Name the target site or starting URL when known.
  • Ask for a bounded, inspectable result.
  • Keep credentials out of the task string and metadata.
  • Use an ordered workflow when exact sequencing matters.

Metadata

Metadata is application-defined JSON returned with the run. Use it for safe correlation values such as a customer ID, job name, or environment. The serialized object is limited to 16 KB.
Metadata and the resolved task are stored with the cloud run. Do not place passwords, session cookies, API keys, or extracted secrets in either field.

Cancel a run

Cancellation is idempotent. A run that is already terminal returns its terminal state.
Last modified on August 17, 2026