Time Trigger Set for Every 3 Days but Firing on Consecutive Days

Questions
1

Hi everyone,

I’m troubleshooting an issue with the Time Trigger node and would appreciate some insight.

Issue
The workflow is configured to run every three days, yet it triggered on two consecutive days right after activation. After that it skipped a day and now seems to be waiting for the next third day as expected.

Question
What could cause the Time Trigger to fire on back-to-back days immediately after activation, despite correct timezone settings and a three-day interval?
Are there known quirks or recommended checks for this behavior?

Thanks for any guidance,

image
image2480×842 290 KB

image
image2429×606 231 KB

image
image3772×917 172 KB

Setup

  • n8n Cloud on Ubuntu (Hostinger)
  • Version: 1.110.1
  • Timezone confirmed as Sydney (AEST) in the workflow and updated correctly in the YAML file.
2

@Inphinity_Design you posted this question twice??

3

Even though they look similar, the core problems are different.

This post is dedicated to understand why every three days trigger is triggering every day?
( other post was focused on NOT triggering triggers.. )

4

Any idea @n8nteam?

5

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