Ask Avvi what is scheduled before anything else. Only work that is still waiting appears there.

An entry that is gone has already been dealt with in some way: it ran, somebody cancelled it, or it failed. The list cannot tell you which, so the record is the next place to look.

An entry that is still listed with a time in the future is the easier case. The time was read differently from how you meant it.

Symptom

The time passed and the change is not in place.

Asking what is scheduled shows the entry with a future time, or does not show it at all.

Cause

Still listed, with a time you did not intend, means the time itself was misunderstood. A time given without a zone is the usual explanation.

Gone from the list means it was handled. It ran successfully, it ran and failed, or somebody cancelled it, and only the record distinguishes those.

Gone from the list with nothing in the record is the awkward case. A scheduled change that needs the on-premises connector is put on hold if those features are switched off for the organisation, and it does not come back when they are switched on again.

A few minutes late is not a failure. Shortly after a deployment it can take longer than usual to start running due work.

Fix

1. Ask Avvi what is scheduled and look for the entry.
2. If it is listed with the wrong time, cancel it and ask again with an explicit date, time and zone.
3. If it is not listed, check the current state. The change may have run exactly as asked.
4. If the state is unchanged, open Logs and filter by that client and the day. A failure is recorded there with its reason.
5. If nothing is recorded at all, treat the scheduled action as lost and create it again.

Making the same request now is the fastest way to understand a recorded failure, because the error you get is the error it hit.

If something doesn’t look right

If Avvi reported success but the change is not in place, check the current state yourself. Some scheduled changes are checked against Microsoft 365 afterwards and some are not, and a check that could not run is reported as success.

If the entry is not listed and you expected it to be, confirm you are on the same client. Scheduled work is listed only for the client it was created against.

If a colleague scheduled it, you will not see it at all. Only the person who created a scheduled action can list it.

If the time and the client are right and nothing was recorded, open a support conversation from the Help drawer with the client, the change, and the time you set.

FAQ

Q: How late is too late?

A: Due work is picked up every half minute. Several minutes is worth investigating, though it can run longer shortly after a deployment.

Q: Why can I not see a cancelled or failed one?

A: The list shows only work still waiting. Anything else has left it.

Q: It says it ran but nothing changed.

A: Check the current state directly. A confirmation is not proof for every kind of change.