Dova Docs22.0.5
Support
Dova 22.0.5Edition 2026.103 min read

Scheduling, time zones and concurrency

Configure recurring Dova execution with an explicit calendar, an IANA time zone and a reviewed concurrency policy.

Complete manual PDF
On this page
  1. Before creating a schedule
  2. Prepare a daily run
  3. Interpret local time and cron
  4. Separate simultaneous runs from parallel tasks
  5. Check and maintain the schedule
  6. When the expected time produces no result

Before creating a schedule

Schedule a Workflow only after it is published and manually tested. Confirm schedule-management and execution permissions, inputs available without browser interaction, authorized Connections and worker capacity. A file attached during a manual test does not become a permanent source for future scheduled attempts.

Open Configuration → Workflow Scheduler to prepare a reusable schedule and assign it from the Workflow. Inspect recurrence, start time, time zone and enabled state in the form. Keep it disabled while reviewing the settings.

Prepare a daily run

  1. Publish and manually run the laboratory Workflow; confirm its output.
  2. Create a recognizable schedule name, such as daily_customers_lima.
  3. Choose daily recurrence at 02:15 and select America/Lima. If using cron representation, the equivalent is 15 2 * * *.
  4. Inspect the calculated next run. The schedule’s zone is independent of the Profile time zone used to display dates.
  5. Assign the schedule to the Workflow and review concurrency. Enable the schedule only after accepting its settings.
  6. After the expected time, find the attempt in Monitor. Check tasks and output: a calculated next date does not prove successful execution.

Interpret local time and cron

ValueInterpretation
15 2 * * *Five fields: minute 15, hour 02, every day.
America/LimaThe example’s IANA zone. 02:15 in Lima corresponds to 07:15 UTC while UTC−05:00 applies.
UTCAnother valid zone; the same cron numbers would produce a different local time in Lima.

Do not substitute an ambiguous abbreviation such as CST for the IANA zone. For zones with daylight-saving changes, review expected behavior around the transition. Recheck the calendar after changing its zone; changing only the language or Profile is not evidence that execution has been rescheduled.

Separate simultaneous runs from parallel tasks

concurrencyPolicy governs overlapping executions of the same Workflow: allow, forbid or replace; the default is forbid. Review it before scheduling potentially overlapping loads. Replacing an execution does not guarantee reversal of external operations that have already occurred.

maxParallelTasks limits parallel tasks within one execution: 1–64, with a default of 4. This does not reserve workers, slots, CPU or target capacity. Actual selection still depends on resources, authorization and availability. A simple sequence makes the first laboratory acceptance easier to interpret.

Check and maintain the schedule

  • Check the published Workflow and versions, assigned schedule and enabled state.
  • Inspect the next run’s time and zone, then compare an actual attempt afterward.
  • Confirm which permanent input was read and where its output was written.
  • When retiring a schedule, inspect existing attempts: disabling future launches does not cancel an active execution.

When the expected time produces no result

First check whether the schedule is enabled and assigned, the Workflow is available and concurrency policy prevented overlap. Then inspect the queue, worker and task errors. Do not create duplicate schedules as a first remedy: they may launch additional writes after the original cause is resolved.

A Timer delays an existing route; it does not replace the Scheduler. Use Monitor and recovery to choose an action appropriate to the observed state.