# Cancel Queued Executions

When a flow uses [throttled or FIFO concurrency](https://prismatic.io/docs/integrations/triggers/fifo-queue.md), requests that arrive while the flow is at its concurrency limit wait in a queue. If something sends an instance far more requests than you expect (a retry loop in a third-party app, a bulk import, or a misconfigured webhook), that queue can grow to thousands of executions. You can cancel the queued executions so they never run, instead of waiting for the queue to drain.

## What gets canceled[​](#what-gets-canceled "Direct link to What gets canceled")

Canceling applies to an entire instance. It cancels every execution that's waiting in a queue for any of the instance's flows at the moment you make the request.

* **Running executions finish.** Canceling only removes executions that haven't started. You can't stop an execution that's already running.
* **New requests still run.** Executions queued after your request aren't canceled. If the source of the extra requests is still sending them, stop it first or the queue will build again.
* **Canceled executions don't run or retry.** Prismatic marks each one with a **Canceled** status and a **Canceled By User** result type, and records who requested the cancellation and when.

Cancellation happens in the background, so it works for queues of any size. Executions that start before the cancellation reaches them run normally.

You can't choose individual queued executions or a single flow to cancel. Canceling queued executions isn't available in the [embedded marketplace](https://prismatic.io/docs/embed/marketplace.md) or the integration designer's test runner.

## Canceling queued executions in the Prismatic app[​](#canceling-queued-executions-in-the-prismatic-app "Direct link to Canceling queued executions in the Prismatic app")

You need permission to edit the instance to cancel its queued executions.

### From an instance's Executions tab[​](#from-an-instances-executions-tab "Direct link to From an instance's Executions tab")

1. Open the instance and select its **Executions** tab.
2. Select the **Queued** (or **Running**) status filter at the top of the page. The **Running now** and **Queued now** [execution load tiles](https://prismatic.io/docs/monitor-instances/executions/monitoring-execution-load.md) appear above the executions list.
3. Click the **⋮** menu on the **Queued now** tile and select **Cancel Queued Executions**. ![Cancel Queued Executions menu on the Queued now tile of an instance\&#39;s Executions tab](/docs/assets/images/instance-queued-now-menu-fcbb2072243be1d168a6146b96a485cd.png)
4. Review the confirmation and click **Cancel Queued Executions**. Click **Keep Queued** to close the dialog without canceling anything. ![Cancel queued executions confirmation dialog](/docs/assets/images/confirm-dialog-3858fed6fca6d8fd9a7106c32b598919.png)

### From the Executions page[​](#from-the-executions-page "Direct link to From the Executions page")

When you're not sure which instance is backed up, start from the **Executions** page in the left-hand sidebar, or from a customer's or integration's **Executions** tab. Select the **Queued** (or **Running**) status filter. The **Top instances by load** tile lists the instances with the most running and queued executions. Click the **⋮** menu beside an instance and select **Cancel Queued Executions**, then confirm.

![Cancel Queued Executions menu on the Top instances by load tile](/docs/assets/images/org-top-instances-menu-750f6b08c56a74b3ada4934840626fd1.png)

Select **Filter to this set** instead if you want to inspect that instance's executions before canceling them.

## Confirming that executions were canceled[​](#confirming-that-executions-were-canceled "Direct link to Confirming that executions were canceled")

After you confirm, Prismatic shows a message that it's canceling the queued executions. Statuses update as the cancellation finishes, so expect a short delay. Large queues take longer to update.

Canceled executions show **Canceled By User** in the **Result Type** column of the executions list.

![Canceled executions in an instance\&#39;s executions list](/docs/assets/images/canceled-executions-list-1b9f78257a5f4082b5a91d839a10f49c.png)

Open a canceled execution to see who canceled it. The **Summary** tab shows a **Canceled By** card, and the **Timeline** tab shows a **Canceled by user** event with the user's name.

![Canceled execution summary showing the Canceled By card](/docs/assets/images/canceled-execution-summary-92386c67f028d38ba95cb09877951cbe.png)

![Canceled execution timeline showing who canceled the execution](/docs/assets/images/canceled-execution-timeline-35023ae20f1a52935352733cb698e3e3.png)

Executions removed with the [clearAllFifoData or removeFifoQueueItems](https://prismatic.io/docs/integrations/triggers/fifo-queue.md#clearing-queued-items) mutations are also marked **Canceled By User**, but no user is recorded, so their **Canceled By** card shows **Queue operation**.

## Canceling queued executions programmatically[​](#canceling-queued-executions-programmatically "Direct link to Canceling queued executions programmatically")

You can cancel queued executions from a script or an operations runbook with the Prism CLI or the Prismatic GraphQL API. Both take an instance ID and follow the same rules as the app: they cancel executions queued at the time of the request, and the cancellation completes in the background.

### With Prism[​](#with-prism "Direct link to With Prism")

Use the `instances:executions:cancel-queued` command:

```bash
prism instances:executions:cancel-queued SW5zdGFuY2U6ZXhhbXBsZQ==

```

### With the GraphQL API[​](#with-the-graphql-api "Direct link to With the GraphQL API")

Use the [cancelAllQueuedExecutionsForInstance](https://prismatic.io/docs/api/schema/mutations.md#cancelallqueuedexecutionsforinstance) mutation:

```graphql
mutation {
  cancelAllQueuedExecutionsForInstance(
    input: { id: "SW5zdGFuY2U6ZXhhbXBsZQ==" }
  ) {
    instance {
      id
    }
    errors {
      field
      messages
    }
  }
}

```

The mutation returns as soon as Prismatic accepts the request, before the executions are canceled. It succeeds even if nothing is queued.

To review canceled executions, query [executionRuns](https://prismatic.io/docs/api/schema/queries.md#executionruns). Canceled executions have a `status` of `CANCELED` and a `resultType` of `CANCELED_BY_USER`. The `cancelRequestedAt` and `canceledBy` fields record when the cancellation was requested and by whom:

```graphql
query {
  executionRuns(
    first: 10
    startedAtGte: "2026-11-17T00:00:00Z"
    startedAtLte: "2026-11-18T00:00:00Z"
  ) {
    edges {
      node {
        id
        instanceName
        status
        resultType
        cancelRequestedAt
        canceledBy {
          name
        }
      }
    }
  }
}

```
