temporalio / temporalio/temporal

Cannot trigger/run multiple schedule actions immediately

Open
#3,614 2 comments 0 reactions 1 assignee View on GitHub

@dnr is already working on this.

Since Nov 20, 2022.

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

Description

Expected Behavior

With either buffer or allow-all, we should support people triggering multiple actions

Actual Behavior

Silently some aren't triggered.

This has been discussed before and it is a known limitation of the system currently. We only allow 1 workflow per second and we can't fail a trigger is within that. This bug is track this known issue in case others see it.

Ideally we should/could change workflow ID to have a unique value put on the end if it duplicates (so no uniqueness value if it doesn't, but maybe starting at -2 if it does). This can be done via an attempted start followed by a counter on already-exists (it's obviously unreasonable to track which ones have already run and we can't guarantee time is monotonic).

Another concern is what if my system clock sync moves me back some seconds to fix skew? Could this cause a duplicate workflow ID?

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.