Jump To

Send the workflow to another step on the canvas and carry on from there, with a per-step limit so a loop cannot run forever.

Quick start

  1. Go to Automate → Workflows and open a workflow. Click + and pick Jump To.
  2. Under Jump to step, pick the step the workflow should carry on at.
  3. Optional: lower Limit jumps to a maximum of from 10 to stop a loop sooner.
  4. Put nothing after the Jump To that must still run — the workflow carries on from the target.
  5. Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.

Watch out

  • A step inside an Ask a Question path, or a send step's failure path, can never be reached. The workflow records jump target not found.
  • The limit is the only thing that stops a loop. Nothing else counts how many times a workflow goes round.
The Add Steps menu open on the canvas, with Jump To highlighted.
The step panel with Jump to step pointed at an earlier step, and the jump limit.
The canvas with a Tag Contact step (Contact tag: vip-customer) followed by a Jump To step.
Details

Getting here

Automate → Workflows, open a workflow, click + on the canvas, then pick Jump To under Add Steps.

Before you start

  • An owner, admin or agent can add this step and save the workflow. Only an owner or admin can publish it, and publishing is what makes it run on live conversations.
  • Building and running workflows depends on your plan; see pricing.
  • The workflow needs at least one other step already on the canvas for Jump To to point at. It cannot point at itself.
  • Nothing outside Inchat has to be connected. The step only changes where the workflow goes next.

Set up

  1. Open the workflow and click + where the jump should happen.
  2. Pick Jump To.
  3. Under Jump to step, choose the step the workflow should carry on at — any step already on the canvas, earlier or later.
  4. Optional: change Limit jumps to a maximum of from its default of 10. Anything from 1 to 10 is allowed.
  5. Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.

Fields

Jump to step
The step the workflow carries on at. The list shows every step already on this canvas, including one nested inside another step.
Limits: It cannot point at the Jump To step itself — the canvas refuses to save that. A step inside an Ask a Question path, or a send step's failure path, is offered here but can never be reached. See Limits.
Limit jumps to a maximum of
How many times this one Jump To may fire before it stops jumping and the workflow carries on with the step after it instead.
Default: 10
Limits: Held between 1 and 10, both as you type it and when the step is saved.

How it works

  • A jump is a go-to. The workflow carries on exactly as if it had arrived at the target step on its own.
  • That means the target runs, then the steps after it on the target's own path, then whatever follows the steps the target sits inside.
  • Nothing placed after the Jump To runs, at any depth, unless the target's own path reaches it. So a jump forward really does skip the steps it passes over.
  • A jump never makes a step run twice in one pass. A step the target's path reaches runs once for that pass, however deeply the Jump To was nested.
  • Each Jump To on the canvas counts its own firings. A second Jump To elsewhere in the same workflow counts separately.
  • Once a Jump To has fired as often as its limit allows, it stops jumping. The workflow carries on with the step after it instead.
  • The count starts again at the beginning of every fresh run of this workflow for the contact.
  • It also starts again whenever a suspended workflow carries on: after a Wait, or after an answered Ask a Question, the rest runs with a clean count.

When it fails

  • The target cannot be reached: the workflow records jump target not found and carries on with the step after the Jump To. This one counts as a failed step in the run's totals, which reaching the limit does not.
  • Four things cause that. The target was deleted from the canvas after the jump was set up.
  • Or it sits inside an Ask a Question path, or inside a send step's failure path — neither is ever searched.
  • Or it sits before a Wait or an answered question that this run has already carried on past. Or Trigger Another Workflow started this run part-way, and the target lies outside that part.
  • You read the outcome in the workflow's Activity tab: pick the run under Execution log, and the step's own line says what happened.

Limits

  • A Jump To's limit bounds that one step only. Two Jump To steps in the same workflow count separately, so a workflow can go round more times than one number suggests.
  • The limit is the only protection against an endless loop. There is no workflow-wide counter behind it.
  • It cannot reach a step in a different workflow. That is Trigger Another Workflow's job, and it has its own separate limit.
  • The target must sit on the main line of the canvas, or inside a Condition segment, a Date & Time branch, a Branch, or one of a Randomizer's own paths. Those are the only places searched.
  • So a step inside an Ask a Question path can never be reached, and neither can one inside a send step's failure path. The Jump to step list offers them anyway.
  • That covers all four of the question's paths: Success, Failure: Invalid, Failure: Timeout and Failure: Sending Failed.
  • It cannot reach a step that came before a Wait, or before an answered Ask a Question, that this same run has already carried on past. Once a workflow pauses and later carries on, only the steps that were still ahead of it exist to jump to.
  • So a backward loop that spans a question or a Wait cannot be built with Jump To. A wait of 15 seconds or less works only until the run's short waits add up past that.
  • Ending the workflow with End stops this run only. The next run starts every Jump To's count from zero anyway.

Best practices

  • Keep the limit low. A small number shows up a mistake on the second or third pass instead of the tenth.
  • Treat the Jump To as the end of its own path. Anything you want to happen afterwards belongs after the target, not after the jump.
  • Use a jump forward to skip a block of steps, and a Condition to decide whether to skip it. The jump moves the workflow; the condition chooses.

Use cases

  • An HTTP Request that failed: a Condition on its result jumps back to the call, with the limit set to 2 so it is tried at most twice more.
  • A path that has already said everything a later block would say: jump forward past that block to the closing step.

FAQ and troubleshooting

Why did the workflow skip my jump and just carry on?
Either the step had already fired as often as its limit allows, or the target could not be reached. Both carry on with the step after the Jump To. Open Activity → Execution log and read that step's line for which one it was.
Do the steps after my Jump To still run?
Only if the target's own path reaches them. A jump is a go-to, not a side trip: the workflow leaves and does not come back. Put anything that must still happen after the target instead.
Can I use Jump To to ask a question again after a delay?
Not by jumping back across the wait. Once a Wait or an answered question pauses the workflow, the steps before that point no longer exist for it to jump to. Build the retry as a new Ask a Question inside the Failure: Invalid path.
Can Jump To send the contact to a different workflow?
No. It only moves between steps on the same canvas. To hand the conversation to another workflow, use Trigger Another Workflow.

Reading this with an AI assistant? Plain Markdown version.