Task · Workflows

Catch up a workflow on tickets already issued

Run a workflow for the tickets that were already there when you turned it on.

7 steps · About 3 minutes

A workflow fires as things happen, so it reaches tickets issued after you turned it on. Tickets issued before that are outside it.

A catch-up fixes that. It works through an event's tickets one at a time and runs the workflow for each one, as if it had been on the whole time.

1. Open the workflow and select Catch up

   Your accountWorkflows

   go.tito.io/acme/admin/workflows

   The button is beside Activity at the top of the workflow.

2. Pick the event

   You're offered the events this workflow covers. The count beside each name is how many tickets it will run for.

3. Choose what it runs as

   The receiving service is told why the workflow ran, and a catch-up names one of the workflow's own triggers. You're offered the triggers about a ticket.

4. Read the count and select Start

   The confirmation names the event, the workflow and the number of tickets about to go through. Read it before you start.

   What goes out can't be recalled.

   You can stop a catch-up part-way, and anything already sent has already arrived. There's no undo on somebody else's system.

While it runs

Starting a catch-up opens its own page. It shows how far it has got, "40 of 4,000 done", and updates itself while the catch-up is live. After about half an hour it stops updating and offers Check now.

1. Select Stop if you need to

   Stopping is immediate and nothing further is sent. What has already gone stays gone.

   To get back to a catch-up later, open the workflow's Catch up page. Earlier catch-ups lists every one it has run, and each row opens its own page.

Running one twice

The form at the top starts a first catch-up. It's refused on an event that's already been caught up for the same reason.

1. Select Run it again on the catch-up in Earlier catch-ups

   The link is on the most recent finished catch-up for an event and reason. It's on that catch-up's own page too. The confirmation says when the last one ran and how many tickets it covered.

2. Say why under Why run it again?

   A line is required. Two catch-ups over the same event and the same reason look identical afterwards, and this is what tells them apart. Write what a colleague would need to know in a month, such as "the badge field was mapped to the wrong key".

   What you write shows on the catch-up's page and on its row in the list.

   Every ticket goes a second time.

   That includes the ones that already went through. A receiving service that treats a second arrival as a new one ends up with duplicates.

   Run one again when the workflow itself was wrong. A field mapped to the wrong key sends blanks, and fixing the mapping doesn't reach the tickets that already went. Running it again does.

   Both catch-ups stay in Earlier catch-ups, each with its own date and count.

   A catch-up that failed or that you stopped can be started from the form at the top instead.

When it stops on its own

A catch-up cancels itself after ten failures in a row, and says so. That's usually the receiving end being down or a key having expired.

What it skips

Voided tickets, and any ticket already queued for this workflow.