Help · Marketing
See what a flow did, and try a run again
Every time a flow runs, ContactRoll keeps what started it, what each condition checked and each step it took. Open a flow and choose Runs to see them, newest first, or What the flows did in Settings, Flows, for every flow.
Find the runs you need
Choose Failed, Waiting or Stopped for a person to see only those runs. A record's history says each time a flow ran on it ("Flow Escalate urgent cases ran: 2 of 3 actions done"); the flow's name opens that run.
You see a run only if you can see the record it ran on.
See what it checked and did
Under a run, choose What it checked and did:
- Started by says which event or time set it off, on which record.
- Conditions lists each condition, what it read on the record, and whether it held. A custom field's value isn't kept here.
- Steps lists each step and what it did, or why it was refused, in words.
A run stopped for a person when its flow paused itself: it had acted on one record ten times in a day, or the organization's flows had done as much as an hour allows. Switch the flow on again from its page when it should go on.
Try a run again
If a step was refused, someone who can edit flows can choose Try again from step 2 (the step that was refused). The steps before it aren't done again. A run that failed completely starts from the beginning, its conditions checked again.
ContactRoll won't try again if the flow was edited or switched off since, the record is gone, or the record was changed after the run — a step meant for the record as it was could be wrong now. It says which. Run the flow on the record again instead.
Runs that fail are tried again by themselves
A run that fails part way through is pending again, exactly where it stood, and ContactRoll tries it again by itself after 1 minute, then 5, then 30. If it fails all three times, it's listed under Failed every retry at the top of the flow's runs, with what went wrong. Someone who can edit flows chooses Replay it to run it again.
A run is never done twice: if ContactRoll stops in the middle of a run, nothing of that run is kept, and the next minute runs it from where it was.
Cancel a run, and how long a run may take
A run that is pending or waiting can be canceled: choose Cancel this run. It does nothing more, and a decision it was waiting for is closed.
On a flow's runs, Longest a run may take sets how many days a run may last from start to end, from 1 to 730. A run still waiting after that is timed out. Leave it empty for no limit: a wait for a date can be years away.
A run's state is one of pending, running, waiting, done, failed, canceled or timed out.
How long runs are kept
What each run checked and did is kept for 30 days. On the Plus plan, someone who can edit flows can keep it for 60 or 90 days. After that the details are cleared; the run's line stays.
Didn’t find what you needed? Ask us on the help center: the form is at the foot of its page, and the people who build ContactRoll answer.