See what a Routine actually did

A Routine that runs unattended is only trustworthy if you can check its work. Every run is kept, whether or not it was delivered anywhere, and every Routine has exactly one conversation thread that all of its runs write into.

One Routine, one thread

Each Routine owns a single persistent thread. Monday's run and next Monday's run land in the same conversation, in order. That is deliberate: you can scroll a quarter of pipeline summaries in one place, and you can reply in the thread to steer the next run without recreating anything.

To open it, go to Routines, open the Routine, and in the Routine history panel click Open Routine history. It opens the exact conversation the runs are writing to. On the console rail, the same threads are grouped under Routine chats.

What the states mean

The badge on a Routine card tells you where it stands:

• Active is scheduled and will fire at the next slot. The card shows the next run time.
• Paused means you stopped it. Nothing fires until you resume. Use Pause Routine and Resume Routine on the detail page.
• Needs attention means TalentOS stopped it because it could not run safely, most often an expired connection. The card carries the reason and usually a link that fixes it.
• Held means a run is being withheld for now rather than cancelled.
• Completed means the Routine reached its end date or its end condition. Its history stays readable.

A Routine in any state other than Active shows no next run time, so an empty Next run is a signal, not a display bug.

Receipts are the record

The Routine thread shows the work. The receipt is the governed record of it: one receipt per run, listing what your Talent actually did, which tools it used, and what it produced. Receipts live in Activity, inside Settings. Go there when you need to answer "did this really send" or "what did it touch", rather than reading back the conversation.

Run it now

You do not have to wait for the next slot. Open the Routine and run it from the detail page when you want to test a change to the instructions, or when you need this week's output early. An on demand run writes to the same thread and produces the same kind of receipt as a scheduled one.

Editing without losing the thread

Edit routine changes the name, category, instructions, schedule, and delivery in place. The thread and the run history stay attached. You do not need to delete and rebuild a Routine to change how it works, and doing that would cost you the history.

Delete Routine removes the standing commitment. Do it when the work is genuinely over, not to reset a bad run.

A worked example

Your Monday pipeline Routine shows Active, but no message reached the team channel. Open Routine history first. If the run and summary are there, open its receipt in Activity and check the delivery step. A failed delivery means the scheduled work ran and only the destination needs attention. An empty history means you should check the next run time, time zone, and end date.

What to check

• No next run time on an Active Routine. Reopen the schedule and confirm the end date has not already passed.
• Runs happen but you never see them. No delivery target is ticked. Add one in Result delivery.
• The thread is empty but the badge says Active. It has not fired yet. Confirm the time zone in the schedule sentence.
• You need proof for someone else. Use the receipt in Activity under Settings, not a screenshot of the chat.

Related