Fix a Routine that is not running

Schedules fire every minute, so a Routine that misses its slot has a reason, and TalentOS records it. Work through this list in order and you will find it.

1. Read the badge

Open Routines and look at the card.

• Needs attention means TalentOS stopped the Routine rather than run it badly. The card shows the reason in plain language, and usually a link straight to the fix.
• Paused means a person stopped it. Open the Routine and click Resume Routine.
• Completed means it reached its end date. Create a new Routine, or edit this one and extend the end date, then resume it.
• Active with no next run almost always means the end date has passed.

2. Reconnect the tool

The most common cause of Needs attention is a connection that expired or was revoked. A Routine runs with your own connected tools, and most connections need re-authorising eventually. When the Monday HubSpot summary stops arriving, HubSpot is the first thing to check.

1. Open the Routine and read the Connections panel. It lists exactly which connections this Routine's work needs.
2. Follow the fix link on the card, or open Connections in the Manage group.
3. Reconnect the tool. Sign in again if you are prompted.
4. Return to the Routine and click Resume Routine.

3. Answer the question your Talent asked

If you set the Routine up by chatting and it never appeared, look in that conversation. An incomplete schedule comes back as a short question rather than a refusal, and the Routine is not created until you answer it.

You will see this when you gave a one-off day with no time ("do this Monday"), or when you said "tomorrow" between midnight and 04:00. Pick one of the offered options and the Routine is created.

You will get a flat refusal, not a question, for cron syntax, an unknown time zone, a time already in the past, or text that carries no time at all. Rephrase using a plain sentence like "every Tuesday at 4pm".

4. Confirm whether it ran but did not reach you

A silent Routine is not always a stopped one.

1. Open the Routine and click Open Routine history. If the run is there, it ran.
2. Check Result delivery in the Routine. If nothing is ticked, results are saved but never pushed.
3. If Slack was ticked and the channel is gone from the picker, use Refresh beside it and select the channel again. Channel lists expire.
4. For a definitive answer, open Activity in Settings and find the run's receipt.

5. Check the instructions, not the schedule

If runs land on time but the output is wrong, the schedule is fine and the brief is not. Open Edit routine and make the instructions specific: name the source, name the fields, say the length, say what to exclude. Then run it once on demand and read the result before waiting another week.

A worked example

A Monday HubSpot summary shows Needs attention and did not reach Slack. Open the Routine and follow its connection warning to reconnect HubSpot. Return to the Routine, choose Resume Routine, and run it once on demand. If history shows a successful run but Slack is still empty, refresh Result delivery, select the Slack destination again, and confirm the delivery in Activity before relying on next Monday's schedule.

What to check

• A Routine pinned to a Skill you no longer have access to will stop. Ask the person who shared the Skill to share it again.
• If the reason on the card mentions setup, open the Routine's source and follow the setup link before resuming.
• If the same Routine blocks repeatedly on the same connection, that connection is being revoked somewhere upstream. Reconnect it, then check whether an admin policy or a password change is expiring it.

Related