polling: enable scheduling policies to avoid concurrency issue.#102
Merged
Conversation
absoludity
commented
Feb 24, 2026
absoludity
left a comment
absoludity
left a comment
Collaborator
Author
There was a problem hiding this comment.
I'm moving ahead to land this small release (which is tested in another PR, and is backwards compatible) so that I can start further work.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using Julee to demo a polling pipeline, I uploaded multiple files, one after the other, which triggered two polling workflows (since I'd updated the schedule to run every 5s). The problem was that the second one ran before the first was finished, so wasn't able to see the previous completion, which caused an error.
Here we introduce a scheduling policy which is passed through to temporal's own schedule config, so that we can SKIP polling workflows while a previous one is running, avoiding the concurrency issue.
I also had the build fail due to a setuptools deprecation coming into effect on Feb 18, 2026. The
licenseis now a string type, not a table type, as per https://packaging.python.org/en/latest/specifications/pyproject-toml/#license (similar for the license classifier).