# Resolve what needs you

> Needs you lists the decisions only you can make, like an edit made during a schedule or a change that failed. Here's what each one means and what to do.

Guides · 2 min read · Updated November 4, 2026

**Needs you** is where Metascheduler puts anything it won't decide for you. You'll find it on the **Calendar** (with a count), in the **Needs you** tab of **Schedules**, and at the top of **Activity**. Items clear themselves once they're fixed, and the same problem is never listed twice.

## What can show up

| Item | What happened | Your choices |
| --- | --- | --- |
| **Changed while a schedule ran** | Someone or something else changed an item, so its old value wasn't put back. | **Restore anyway** or **Keep current** |
| **Changes failed** | Some items couldn't be changed when a schedule started or ended. | **Retry** or **Dismiss** |
| **Needs access** | A change needs access the app doesn't have. | **Grant access** or **Dismiss** |
| **More than a day late** | A one-time change didn't run on time. | **Run now** or **Skip** |
| **Didn't start** | A start was due while the app couldn't run it, and its window had already ended. | **Dismiss** |
| **Doesn't reach all buyers** | A followed rollout reaches only part of your traffic, but your changes apply to everyone. | **Got it** |
| **Rollout deleted** | A followed rollout was deleted, so the schedule ended as if it concluded. | **Dismiss** |
| **Schedule paused** | Your plan doesn't cover the schedule any more. | **See plans** or **Dismiss** |

## Someone changed it

At the end of a schedule, Metascheduler only puts back an item that still has the value it wrote. If the value is different, someone (or another app) changed it, and their change is left alone.

- **Restore anyway** writes the value from before the schedule. If another live schedule also changes it, Metascheduler asks you to confirm, because that schedule's change would be lost until it runs again.
- **Keep current** leaves the item as it is now.

> **Try it:** [What happens when someone else changes it](https://metascheduler.app/help/needs-you)

## A change failed

Open the item, or the run in **Activity**, to see each failed item and why. **Retry** runs only the failed items again. Common reasons:

- **The app doesn't have access to make this change.** Grant access and retry.
- **Shopify didn't accept the change.** Open it to see Shopify's message, such as a value that isn't allowed.
- **The item no longer exists in your store.** Remove it from the schedule.
- **Shopify was busy or unreachable.** Metascheduler already retried a few times. Retrying again usually works.

> **One item doesn't stop the rest**
>
> A failed item never stops the other items in the run. The run shows **Partly done**, and only the failed items need a retry.

## Missing access

**Grant access** opens Shopify's permission prompt for the access the change needs, then retries the failed changes. See [Access and permissions](https://metascheduler.app/help/access-and-permissions.md).

## Related articles

- [How reverting works](https://metascheduler.app/help/undo-and-drift.md): Metascheduler saves what it replaces and checks before it puts it back, so it never overwrites an edit someone made in the meantime.
- [Access and permissions](https://metascheduler.app/help/access-and-permissions.md): What Metascheduler asks Shopify for, when it asks, and how to grant or revoke each kind of access.
- [How scheduling works](https://metascheduler.app/help/how-scheduling-works.md): Schedules, timing, changes, windows and runs: the ideas behind Metascheduler, and what happens at each moment.