Browser automationQueue and execution

Queue and campaigns

Connect simulation crons, operator campaigns, account actions, and worker claims without duplicate execution.

Queue and campaigns — contract and behavior

  • Simulation endpoints enqueue bounded platform actions; the campaign scheduler expands operator-defined campaigns into the same queue.
  • The queue row is the durable handoff between content policy and browser execution.
  • Worker eligibility and platform/account data are resolved before launching the trajectory.
  • Retries preserve action identity so replay, diagnostics, and campaign state can distinguish a retry from a new action.

Stay in the loop. Never miss out.

Subscribe to our newsletter and unlock Wisent insights.