# A trigger didn’t fire

You expected a run, but Runs shows none. Find what you see below.

![A schedule on a Draft workflow: the panel says Once published, the next runs, and lists weekdays only.](https://docs.gorunner.io/img/build/tdf-1-light.jpg)

The schedule’s own panel names the two likeliest causes: it isn’t published, and it skips weekends.

- [The workflow says Draft](https://docs.gorunner.io/build/a-trigger-didnt-fire#not-published): Not published
- [The workflow says Paused](https://docs.gorunner.io/build/a-trigger-didnt-fire#paused): Unpublished
- [“Webhook not found.”](https://docs.gorunner.io/build/a-trigger-didnt-fire#webhook-not-found): The address
- [“Webhook authentication failed.”](https://docs.gorunner.io/build/a-trigger-didnt-fire#auth-failed): The sender
- [“HTTP method not allowed for this webhook.”](https://docs.gorunner.io/build/a-trigger-didnt-fire#method-not-allowed): The sender
- [“Request body too large.”](https://docs.gorunner.io/build/a-trigger-didnt-fire#body-too-large): The sender
- [“Too many runs of this workflow are waiting.”](https://docs.gorunner.io/build/a-trigger-didnt-fire#line-full): The line
- [“This endpoint isn’t accepting requests right now.”](https://docs.gorunner.io/build/a-trigger-didnt-fire#not-accepting): The organization
- [No runs on Saturday or Sunday](https://docs.gorunner.io/build/a-trigger-didnt-fire#weekends): A schedule
- [Runs start at the wrong hour](https://docs.gorunner.io/build/a-trigger-didnt-fire#wrong-hour): A schedule
- [Some runs never started](https://docs.gorunner.io/build/a-trigger-didnt-fire#refused): The limit
- [Rows or emails that were already there didn’t start runs](https://docs.gorunner.io/build/a-trigger-didnt-fire#already-there): An app’s trigger
- [An app’s trigger picks up nothing](https://docs.gorunner.io/build/a-trigger-didnt-fire#app-trigger): An app’s trigger

## The workflow says Draft

**Why**

Only a **Live** workflow’s trigger starts runs. A draft runs only when you press **Test**.

**Fix**

1. Open the workflow.
2. Press **Publish**. The state next to its name changes to **Live**.

## The workflow says Paused

**Why**

Someone pressed **Unpublish**. The trigger stopped, and a schedule’s panel says **Paused — no runs until it is turned back on**.

**Fix**

1. Open the workflow and press **Publish**.

## “Webhook not found.”

**Why**

The address answers `404` with this text when the workflow isn’t **Live**, and when someone pressed **Regenerate URL**: the old address stops working at once. It does the same when the trigger’s app isn’t allowed for your organization. A form’s address answers like a webhook’s.

**Fix**

1. Make sure the workflow is **Live**.
2. Select the trigger’s card and copy its current **Webhook URL (production)** or **Form URL (public)**.
3. Give the new address to whatever sends to it.

## “Webhook authentication failed.”

**Why**

The sender didn’t pass the trigger’s **Authentication**, such as a missing header or a wrong password. With a signature check, it says **Webhook signature verification failed.**

**Fix**

1. Select the trigger’s card and read its **Authentication**.
2. Make the sender send exactly that.

## “HTTP method not allowed for this webhook.”

**Why**

The request’s method isn’t in the trigger’s **Allowed Methods**.

**Fix**

1. Select the trigger’s card and add the method to **Allowed Methods**, or leave it empty to allow every method. Then press **Publish**.
2. Or make the sender use a method that is allowed.

## “Request body too large.”

**Why**

The request is over 5 MiB.

**Fix**

1. Send less, or a link to the file.

## “Too many runs of this workflow are waiting.”

**Why**

The workflow’s line is full.

**Fix**

See [Limit runs at once](https://docs.gorunner.io/build/runs-at-once).

## “This endpoint isn’t accepting requests right now.”

**Why**

The organization is suspended, or on Self-hosted the installation has no valid license. The sender is told to try again in an hour.

**Fix**

Ask GoRunner support, your platform admin or, in the Embed, your provider.

## No runs on Saturday or Sunday

**Why**

**Every Hour** and **Every Day** run on weekdays only, unless you tick **Run on weekends (Sat, Sun)**.

**Fix**

1. Select the **Schedule** card and tick **Run on weekends (Sat, Sun)**.
2. Check the next runs at the top of the panel, then press **Publish**.

## Runs start at the wrong hour

**Why**

A schedule uses its own **Timezone**, which is UTC until you change it.

**Fix**

1. Select the **Schedule** card and set **Timezone**.
2. Check the next runs, then press **Publish**.

## Some runs never started

**Why**

The workflow was at its **Concurrency limit**, set to **Refuse**. New runs are turned away: a webhook caller gets `429` with **This workflow is already running its limit of 2 at once.**, a schedule skips its turn, and an app trigger tries the items again at its next check.

**Fix**

1. Open the workflow’s **Settings**.
2. Under **When it is at its limit**, choose **Wait in line**, or raise the **Concurrency limit**.

## Rows or emails that were already there didn’t start runs

**Why**

The first check after you publish only notes what is already there. Only items that arrive or change after it start runs. Changing what the trigger watches, such as its sheet, folder or connection, starts over the same way.

**Fix**

1. Add a new item, or change one.
2. It starts a run within about a minute.

## An app’s trigger picks up nothing

**Why**

Triggers such as Gmail’s check for new items about once a minute, through their connection. A connection that is **Signed out** can’t check.

**Fix**

1. In the sidebar, open **Connections**.
2. Find the app’s connection and press **Sign in again**.

## Still stuck?

Write to [GoRunner support](https://gorunner.io/contact). Send the workflow’s name, its trigger, and when you expected the run.

Source: https://docs.gorunner.io/build/a-trigger-didnt-fire