Skip to content

States and lanes

The bricks below are drawn with the app’s own colours and glyphs, so they look the same here as on the batch screen. Every colour comes with a glyph, so none of them depends on telling colours apart.

Shown in the header of each step’s column.

BrickKindWhat it means
Company step
company
Runs your code once for each company. Most steps are this kind.
Batch step
batch
Runs your code once over every company that reached it, after none are still on their way. Use it to compare companies, such as finding duplicates.
Checkpoint
checkpoint
Runs no code. Holds every company until a time, an event, or someone releases it.
Changeset
changeset
Runs no code. Seals the CRM changes proposed so far into one package for an approver.

One company at one step.

BrickStateWhat it means
Pending
pending
The company hasn't reached this step yet.
Ready
ready
Queued: it runs as soon as there's room.
Running
running
The step is running for this company now.
Retrying
retrying
The last run failed in a way that may pass on a second try, such as a timeout or a rate limit. It runs again after a pause.
Asked
asked
The step asked a question and waits for someone to answer it.
Done
done
The step finished and saved its facts.
Skipped
skipped
The step's when condition didn't match this company, so it didn't run.
Failed
failed
The step threw an error, or used up its retries. The company is parked until someone retries it.
Parked
parked
The step stopped on purpose: it hit a spending cap, a provider ran out of credit, or the step is waiting on a timer (ctx.wait) and runs again later.
At barrier
barrier
The company is through everything before this step, and waits here for the rest of the batch.
Approval
approval
The company's CRM changes are sealed in a changeset that waits for an approver.
Writing
writing
The changeset was approved and Motions is applying it to the CRM.
Passed
passed
The checkpoint was released, or the changeset was written.
Stopped
stopped
This step won't run: the company left the batch, or its changeset was rejected.

Where a company is in the batch as a whole. Done, held and dropped are final: the company is out of the batch.

BrickStateWhat it means
Done
done
Through every step.
Moving
active
Steps are running or queued for it.
Waiting
waiting
A step asked a question; the company waits for the answer.
Parked
parked
It stopped and needs someone: a step failed, hit a spending cap or ran out of provider credit. A company whose step is waiting on a timer shows here too, until the step runs again.
Held
held
Kept out of this batch on purpose: a step or an answer held it, or its changeset was rejected.
Dropped
dropped
Removed from the batch, with a reason such as no domain or outside the ICP.
State
approval Sealed and waiting for an approver.
approved Approved, and about to be written.
writing Being written to the CRM.
done Every operation has a receipt.
rejected An approver rejected it. Nothing was written.
Receipt
written The CRM has it.
skipped Nothing was written, with the reason: already up to date, already exists, or the connection is read-only.
failed The CRM refused it, with its error.
State
open Waiting for an answer.
answered Someone, or the step with a low-risk suggestion, answered it.
defaulted Its deadline or a checkpoint’s cutoff passed, and it took the queue’s default.

Motions is built by Pruma. These docs describe what the platform does today; Limitations lists what it doesn't do yet. Open the app