Runs onWrit CloudDesktopSelf-hosted
On this page
Wait for change
The wait_for_change step blocks until the watched region updates — after a filter applies, a sort re-renders, or new results stream in — so the next step reads fresh state.
In a workflow, this is a step object with "type": "wait_for_change". Steps run in order, and each step can read the outputs of the steps before it. See the full workflows reference for the 30+ step types.
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Fields
| Field | Type | Description |
|---|---|---|
selector | selector | The region to watch for a change; the page when omitted. |
Example
A single wait_for_change step as it appears in a workflow's steps array:
{
"type": "wait_for_change",
"config": { "selector": "#results" }
}How it behaves
- Ideal after applying a filter or sort that re-renders a list.
- Pairs with scroll to wait until lazy items have loaded.
Where it runs
The wait_for_change step executes wherever the run executes. On your local or BYO agent there is no compute charge and the agent can reach intranet-only systems; on Writ cloud the run is metered by running time (~$0.12 per browser-hour, from your plan’s included usage wallet.
What next
- Workflows - the full step vocabulary and the workflow object.
- Recorder - capture steps by clicking through a site.
- Managed endpoints - turn the workflow into a REST endpoint, or an MCP tool.