Duaer

Integrations

Common issues with Schedule Trigger in Duaer

Common Schedule Trigger issues in Duaer: invalid cron expressions, runs at the wrong time, and interval changes that do not apply.

Invalid cron expression

With Trigger Interval set to Custom (Cron), Duaer could not read your expression. Check that:

  • It follows the examples on the node. A first seconds column makes six fields; without seconds there are five.
  • With the seconds column removed, it validates on crontab.guru.

Runs at the wrong time

Usually the time zone. Change it for the instance or for one digital organization:

  • Self-hosted Duaer: set the instance time zone with GENERIC_TIMEZONE.
  • One digital organization: open settings from the menu at the top right of the canvas, change Timezone, and save.

A new interval or variable does not apply

Schedule Trigger reads its interval, and any variables in it, when you publish. After publishing, unpublish and publish again for a change to apply.

The schedule counts from the moment you publish. For example, hourly with a run due at 12:00, changed to every 2 hours and republished at 11:30, next runs at 13:30.

Questions

Why does the Duaer Schedule Trigger run hours off?

Usually the Duaer time zone. Change Timezone in the digital organization settings, or have a self-hosted admin set GENERIC_TIMEZONE.

Do I need to republish after changing a Duaer Schedule Trigger interval?

Yes. Duaer reads the interval on publish, so unpublish and publish again for the new interval to apply.

In this section