> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/bulk-price-editor-sami/faqs/task-stuck-pending-or-scheduled.md).

# Why is my task stuck in Pending or Scheduled?

A task shows Pending execution or Scheduled and does not seem to start.

## Pending execution

The task has been told to start and is waiting for Shopify to accept its bulk operation. This is normal for a minute or two, longer if another bulk operation is already running in your store (another task from this app, an import in the Shopify admin, or another app). It starts automatically when the queue is free.

If a task stays in **Pending execution** for a long time, check the Tasks list for a **Running** task, wait for it to finish, and refresh. If nothing is running and the task still does not start, contact support with the task ID.

## Scheduled

The start time has not arrived yet. Check three things:

1. **Timezone.** The scheduled time is in the timezone shown in **Settings › Timezone**, not necessarily your computer's. See [Set your timezone](/bulk-price-editor-sami/settings-and-plans/timezone.md).
2. **Date.** Open the task; the **Task status** card shows **Scheduled for \<date> at \<time>**.
3. **Recurring.** Recurring occurrences are picked up every 10 minutes, so a run can begin up to about 10 minutes after the time you set.

To start a scheduled task right away, choose **Apply change now** from the **⋮** menu.

## Manual start

A task with the badge **Manual start** never starts by itself. Choose **Apply change now**, or open the task and set a **Start time**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.samita.io/bulk-price-editor-sami/faqs/task-stuck-pending-or-scheduled.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.