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.
Specifications
- Version: temporalio==1.18.2 (UI 2.25.0)
- Platform: Debian
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:
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.
Specifications