24/7 development

Hand the Scan → Start loop to Expecto Centum. Once it's running, a workflow keeps checking your tracker for new tickets and works through them on its own — overnight, over the weekend, or only during the hours you choose.

Turning the mode on doesn't start anything by itself. You switch it on, then start it — with your next Scan, or at a time of day you pick. From then on there's nothing to press: the app scans, runs what it finds, and checks again on the interval you set, for as long as it's open. Closing and reopening the app picks the session back up where it was.

I Switch it on

Open Config → Workflow, pick the workflow, and select its scanning stage in the list on the left. The 24/7 development section sits with that stage's other settings.

1. Switch it on.
2. Set Scan every (minutes) to how often it should check for new work. It starts at 60.
3. Under Starts, keep On your next scan, or choose At a set time and pick the time.

The section then reads Armed or Scheduled — nothing is scanning or running yet. If the workflow starts with Specifications, switching 24/7 on moves its first stage to Ticket Scanner for you and says so.

II Choose when it runs

By default it runs at any hour, every day. To keep it to certain times:

• Active window — switch from Any time to Between the hours of and pick a start and end. A window that ends before it starts runs overnight — 23:00 to 05:00, say.
• On these days — tick the weekdays it may run, such as Monday to Friday. At least one day stays ticked; to stop it altogether, switch the section off.

A start time has to fall inside the active window. If it doesn't, the section and the dashboard both read Won't start until you move one of them. Times follow your computer's clock and are written the way your region writes them.

III Start it

• On your next scan — close Config and press the workflow's Scan button, the same one you use to fetch tickets by hand. Confirming the scan starts the session: the app runs what it found and checks again one interval later. Until then the mode simply waits, even across restarts.
• At a set time — there's nothing to press. At that time, on the next day you've ticked, the app scans and starts on its own. If the app is closed then, the session starts as soon as you open it.

IV Watch it

While the mode is on, a gold 24/7 Mode panel sits on the dashboard, beside the Spec board button. It tells you what happens next:

• Starts on your next scan or Starts 22:00 — switched on, waiting to begin.
• Next check in 12 min or Next check 15:30 — when it will next look for work. Checking for work… while it looks.
• Waiting for the run to finish — the app works through one run at a time, so the next check follows the current run.
• Resumes Mon 09:00 — outside your active window, or on a day you left unticked.

The Spec board stays open throughout, so you can reorder the queue, park cards in Backlog and read what ran.

V More than one workflow

Each workflow has its own switch and its own session, and every workflow with the switch on keeps going whichever one you have open. They share one thing: the app runs one run at a time, so when two sessions fall due together, one waits for the other's run to finish. Config names any other workflow that has 24/7 on, with its schedule, so you can set start times and intervals apart. On a workflow with the mode off, an outlined Off here panel names the workflow it's running for, with a button to switch to it — and if a run there fails, a notice says so until you dismiss it.

VI Turn it off

While a session runs, the workflow's Scan and Start buttons are gone — the session launches everything. To end it, click Turn off 24/7 in the panel, or switch the option off in Config; both do the same thing. Whatever is running finishes normally, nothing new is picked up, and the buttons come back.

✦ Good to know

• Keep the app open. The loop runs in the app, so closing it pauses the scanning. Reopening it resumes the session with nothing to press.
• It scans the filters you've ticked for the scanning stage. Check them before the session starts — a session set to start at a time never shows you the Scan dialog.
• Finished work isn't redone. Tickets already processed are skipped; only new or updated ones come through.
• Nobody is asked to approve. Runs the session launches open their pull requests without the approval dialog, even with Ask before landing switched on, so the session never stalls waiting for someone who isn't there. Runs you start yourself still ask.
• It switches itself off if it hits a wall — a connection that needs signing in again, or setup that's missing — and tells you. Fix it, switch the mode back on, and start it again. A tracker that can't be reached for a moment isn't a wall: you're told once, and it keeps checking.
• Your plan and sign-in count. Signing out, or your plan dropping below Hundredfold, switches the mode off with a notice saying why. Scanning and running work yourself carries on as normal.
• A sleeping computer skips the checks it sleeps through. Waking it doesn't set off a check; the session waits for its next scheduled one.