Start and stop a rack

Your browser drives the Mac. The Mac drives the phones. The browser never touches a phone, which is what lets you run a rack from anywhere without anything sensitive leaving the room the phones are in.

How a command reaches a Mac#

1. You press Start

   Recorded against one Mac in your Workspace, not broadcast to all of them.

2. The Mac asks for work

   Each Mac checks in on its own. No inbound connection, no port to open.

3. It is handed only what it understands

   A Mac declares which kinds of command it can carry out and is handed nothing else, so an older build cannot be given an instruction it would misinterpret.

4. It reports back

   What ran, what it did, what failed. That fills Activity.

A Mac holding work is asked to come back in 30 seconds, so starting a rack is quick rather than instant.

Stopping#

Not a kill. Work in flight finishes the action it is on, because interrupting a phone halfway through a Post can leave a half written caption on a real Account.

A Device you stopped goes to Paused and stays there. That is not the same as Needs attention: Paused is your decision, and tame will not quietly resume it.

Immediate Sessions and scheduled warmup#

• Warm now requests one Session for the selected Account. Warm & search also requests a search using its saved niches. Both leave the schedule unchanged and can start outside waking hours.
• Start scheduled warmup enables each included Account's planned day, within its waking hours. Pause schedule pauses future scheduled Sessions and lets the current Session finish.
• Stop Session requests a stop of the current Session. It does not turn off the ongoing schedule. See Warmup settings.