Timing: where it lives
A campaign has no timing of its own. It answers whenever it is called: the cascade picks the next message for the contact and returns it, every time.
Where timing is set
- A HubSpot workflow (Professional and above): the delay in the loop (Get Next Message, send, delay, Loop) is the time between sends. A 3 day delay sends at most once every 3 days.
- A flow in mxAURA: its pace (cadence) decides when each contact is called.
Nothing on the campaign page holds a send back. A priority row goes first when the campaign is next called; how soon that is depends on the flow or the workflow.
The HubSpot loop
Branch on Status:
- Status is Message: send the email, delay, Loop.
- Status is Skip: the contact is done; end.
- Status is Error: notify someone; end.
- Status is Hold: end; mxAURA finishes that contact on its own.
A loop with no delay sends on every turn.
Before v3.1.941
Campaigns had Days between sends and Hours after priority, and a dispatch answered Skip with the Code TOO_SOON when a send was too close to the last one. That is gone: the setting is off the page, the dispatch never answers TOO_SOON, and an old TOO_SOON branch in a workflow simply never fires.