temporalio / temporalio/temporal

Schedule with microseconds in offset launches only once

Open
#10,312 2 comments 0 reactions 2 assignees View on GitHub

@chaptersix is already working on this.

Since May 28, 2026.

potential-bug schedules
Dominant language
Go
Stars
23.2k
Forks
1.9k
Avg merge
2d 8h
Merged PRs (30d)
228

Description

Expected Behavior

A schedule launches workflows as defined in ScheduleIntervalSpec when its offset contains microseconds.

Actual Behavior

A schedule launches only one workflow as defined in ScheduleIntervalSpec when its offset contains microseconds.

Steps to Reproduce the Problem

Define ScheduleIntervalSpec with an offset containing microseconds and send a schedule.
Python SDK:

temporal_client = await client.Client.connect(TEMPORAL_ADDRESS)
interval = timedelta(seconds=120)
offset = timedelta(seconds=63, microseconds=123)

schedule_spec = ScheduleSpec(
    intervals=[ScheduleIntervalSpec(every=interval, offset=offset)],
)
schedule = Schedule(
    action=ScheduleActionStartWorkflow("workflow name", None),
    spec=schedule_spec,
)

await temporal_client.create_schedule("bug-repro-schedule", schedule)

The first schedule has an offset with microseconds, and the workflow is only launched once (the upcoming runs should have already passed).
The second schedule doesn't have microseconds in its offset, and the workflow is launched according to the specified interval and offset.

Image

Specifications

  • Version: temporalio==1.18.2 (UI 2.25.0)
  • Platform: Debian

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.