My reminder did not run

What you are seeing

You set something up, the time came and went, and nothing arrived — no message in the conversation and nothing on the bell.

Before anything else, open the Task agent and find the job. Almost everything below is answered by what that screen shows you: whether it is still switched on, when it last ran, and when it next will.

If the job is not in that list at all, it was never created. That happens when a request was read as a question rather than an instruction — ask again, plainly: "Schedule this: every Monday at 8am, …"

Check the time and time zone you gave

This is the most common cause by a distance, and it does not look like a time zone problem — it looks like nothing happened.

Times are recorded in your profile's time zone unless you named a different one when you asked. If your profile says one place and you are in another, a job set for 8am runs at 8am in the profile's zone.

• Check the time zone on your profile is where you actually are.
• Check the job's next run time in the Task agent — it is shown in the job's own zone.
• Fix it in a message: "change that to 8am London time".

Also worth ruling out: every Monday means the next Monday, so a job created on a Monday afternoon first runs a week later, not that morning.

Check it is not paused

A job that is switched off stays in the list and does nothing. Two ways it gets there:

• You paused it, possibly a while ago. Ask Orsola to start it again, or turn it back on from the Task agent.
• Orsola switched it off. A job that fails five times in a row is switched off automatically, so something broken does not keep costing you credits every run. Any single success resets that count, so this only happens to something that is properly stuck.

If it was switched off for failing, fix the cause before turning it back on — the two sections below are the usual reasons — otherwise it will fail five more times and switch itself off again.

Check your credits and your plan

A scheduled run costs credits exactly like a message you type. With none left, runs fail, and five failures in a row switch the job off.

Your balance is on the Dashboard; you top up from Subscription. If it is empty or close to it, add credits or wait for your monthly allowance to renew, then switch the job back on — see check your balance and usage.

Why can't I send a message? covers the same cause showing up in a conversation, and what credits are, and what uses them explains what a run costs.

Check a connected account has not dropped out

If the job reads your mail, your calendar or your files, it needs that account connected at the moment it runs — not just when you set it up. Connections lapse: a password change, a revoked permission, or an expired authorisation will do it.

Open Integrations and look for anything asking to be reconnected. Reconnect it, then switch the job back on if it had been stopped. Review, reconnect, or remove a connection has the detail.

Still stuck

If the job is active, the next run time is right, you have credits, and every account it needs is connected, then it is not one of the ordinary causes.

Get in touch and include what the job is meant to do, the time and time zone you set, and when you last saw it work. That is enough for us to find it; without it we are guessing.