Routing Timing and Order

Routing is asynchronous

When a record reaches the Distributely action in a HubSpot workflow, the action hands the record over and the workflow moves on. Routing happens immediately afterward, not during the step.

The practical effect: the owner appears on the record a moment after the workflow step completes, not at the same instant. For a single record this is usually a second or two.

This also means the workflow step's own status tells you the request was accepted, not that an owner was written. A green step in HubSpot is not proof of an assignment. Confirm outcomes in Distribution Analytics or on the record itself.

If you have a step immediately after the Distributely action that reads the owner, add a short delay before it. Otherwise it can read the record before the owner lands.

One at a time, in order

Records for a single portal are processed strictly one at a time, in the order they were received.

This is deliberate, and it is what keeps round robin fair and correct. Rotation depends on knowing who received the last record. If two records were routed at the same instant, both could pick the same next person, and your rotation would drift. Processing them in sequence means each assignment sees the result of the one before it.

Your portal's records never compete with another customer's. The ordering applies to your portal alone.

What this means for batches

Enrolling a large batch at once means those records route sequentially. The first record in the batch routes right away. The last one waits for everything ahead of it.

So a bulk enrollment of a few thousand records will take noticeably longer to finish than a single record does, and the last record in the batch is the one that waits longest.

What is normal

• An owner appearing a second or two after the workflow step on a single record.
• A batch taking progressively longer to finish as it gets larger, with early records done quickly and later ones arriving over time.
• Records arriving in the order they were enrolled.
• A short delay needed before any workflow step that reads the newly assigned owner.

How long should a single record take?

A second or two in normal conditions. Longer if a batch is ahead of it.

I enrolled two thousand records. Why is the last one still waiting?

Because the records ahead of it are being routed one at a time, in order. That sequencing is what keeps the rotation correct. The batch will finish, and nothing in it is lost.

Could a record be skipped in a large batch?

No. Ordering is preserved and every record is processed. A record that ends with no owner failed for a configuration reason, not because it was skipped. 

My next workflow step reads the owner and sees nothing.

It ran before routing finished. Put a short delay between the Distributely action and any step that depends on the owner.