Stop all and Activity

Stop all

Stop all is the kill switch. While it is on:

• your schedules are paused;
• your running replies are stopped;
• no write runs: an app action, an automation run, a deploy, a workspace change or a new schedule is refused, with the reason (removing a schedule still works).

Reads and the chat go on, so you can ask what happened.

Turn it on with the app's Stop everything button, /stop-all, or crewdesk stop-all; lift it with /stop-all off, Resume, or crewdesk stop-all --off. You can add a reason, which is kept and shown.

An organization's admins can stop the whole organization (/stop-all org, crewdesk stop-all --org). Setting and lifting are both recorded: who, why and what it touched.

/stop (or Ctrl+C in the terminal) is the small version: it stops the one reply that is running.

Activity

Activity is what Crewdesk did on your behalf, newest first:

Category	Examples
write, send	A record updated; an e-mail, message or post sent
run	An automation run
deploy	A deploy to AMP
schedule	A schedule made, removed, run, failed, paused or resumed
workspace	Changes in a folder
approval	A card you answered
refusal	A write refused, a limit hit
stop	Stop all set or lifted

Reads are left out. Each item links back to its chat. Only your own activity is shown, and no item holds the values of what was written.

Open it with the app's Activity button or /activity; in the terminal, /activity sends runs filters and /activity open N opens an item's chat; from the shell, crewdesk activity.

Notices

When one of your schedules pauses (three failures in a row, or the automation changed), you get a notice: a banner in the app or a note in the terminal the next time you open it.