# Schedule Trigger either not triggering or triggering at the wrong time

**URL:** <https://community.n8n.io/t/schedule-trigger-either-not-triggering-or-triggering-at-the-wrong-time/226897>\
**Category:** Questions\
**Tags:** core, trigger, schedule-trigger\
**Created:** [November 26, 2025, 1:25pm UTC](https://community.n8n.io/t/schedule-trigger-either-not-triggering-or-triggering-at-the-wrong-time/226897 "2025-11-26T13:25:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Schwalbi](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@Schwalbi](https://community.n8n.io/u/Schwalbi)\
**Post date:** [November 26, 2025, 1:25pm UTC](https://community.n8n.io/t/schedule-trigger-either-not-triggering-or-triggering-at-the-wrong-time/226897/1 "2025-11-26T13:25:57Z")

</div>

## Describe the problem/error/question

I have two workflows with a daily schedule trigger.

One of them is not working at all. Although I deactivated the node/flow (with a short break) nothing works for me.

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/a/f/af370a6cf02ac88c0bdbbbaf5b1da06e67ffc136.png)

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/8/1/81c619ddb97c7300903d552975370915b37373eb.png)

I have set my Timezone for the workflow correctly

The second also runs on a daily basis and is supposed to run at 11:15, but triggers at around 6pm or sometimes never.

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/f/a/fa2a765994a7394224eaeb03269521b28a90d941.png)

The triggers that are supposed to run every e.g. two minutes work perfectly fine. I’m only having trouble with the daily ones.

## What is the error message (if any)?

None

## Please share your workflow

Trigger 1

Trigger 2

## Share the output returned by the last node

None

## Information on your n8n setup

- **n8n version:** 1.119.2 (older versions didn’t work as well)
- **Database (default: SQLite): default**
- **n8n EXECUTIONS\_PROCESS setting (default: own, main): default**
- **Running n8n via (Docker, npm, n8n cloud, desktop app): Docker(Compose)**
- **Operating system: Debian (Raspberry Pi OS)**

---

<div class="post-metadata">

**Author:** ![Parintele\_Damaskin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/parintele_damaskin/32/139243_2.png) [@Parintele\_Damaskin](https://community.n8n.io/u/Parintele_Damaskin)\
**Post date:** [November 26, 2025, 2:05pm UTC](https://community.n8n.io/t/schedule-trigger-either-not-triggering-or-triggering-at-the-wrong-time/226897/2 "2025-11-26T14:05:24Z")

</div>

Hey @Schwalbi !

I feel you… had same issue and I switched to Custom Cron(and never had any issue so far).

Set Trigger Interval to Custom (Cron), ennnter the following cron expression:

15 11 \* \* \*

This means: at minute 15, hour 11, every day.

Give it a try!

> [@Schwalbi](#):
>
> have set my Timezone for the workflow correctly

You can set the timezone globally for the instance, for individual workflows, or both. If you do not set it for a workflow, the instance (global) timezone is used.

---

<div class="post-metadata">

**Author:** ![Schwalbi](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@Schwalbi](https://community.n8n.io/u/Schwalbi)\
**Post date:** [November 26, 2025, 2:26pm UTC](https://community.n8n.io/t/schedule-trigger-either-not-triggering-or-triggering-at-the-wrong-time/226897/3 "2025-11-26T14:26:28Z")

</div>

Hi @Parintele_Damaskin, thanks for you advice,

I suspected that I might have to use the custom cronjob. I have set the timezone for both workflows individually.

Hope they fix it one day 😃

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [February 24, 2026, 2:27pm UTC](https://community.n8n.io/t/schedule-trigger-either-not-triggering-or-triggering-at-the-wrong-time/226897/4 "2026-02-24T14:27:11Z")

</div>

Closed on February 24, 2026, 2:27pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
