Skip to content

First run of a new job is never persisted to dynamodb#1109

Draft
CharlesPeacock wants to merge 1 commit into
masterfrom
TRON-2673-first_run_of_a_new_job_is_never_persisted_to_DynamoDB
Draft

First run of a new job is never persisted to dynamodb#1109
CharlesPeacock wants to merge 1 commit into
masterfrom
TRON-2673-first_run_of_a_new_job_is_never_persisted_to_DynamoDB

Conversation

@CharlesPeacock

Copy link
Copy Markdown
Contributor

This PR aims to fix a bug where Tron did not to attach a watcher to the first run of a new job. Interestingly enough, this bug has existed for several years now; since 85% of Tron jobs run every 20 minutes or so, this went unnoticed for a while since reaching the run_limit for a given job removes the old runs from the tail.

This will help heavier, less frequent job runs in ensuring data integrity and consistent observability across Tron. A unit test has been added to assert old behavior is no longer present.

All tests pass, keeping as draft PR for the time being until I verify more job runs on my local env.

@CharlesPeacock CharlesPeacock changed the title add initial fix and unit test map_to_job_and_schedule First run of a new job is never persisted to dynamodb Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant