Don't run application recurring jobs in betas #2243
Merged
Conversation
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
Betas use the same application DB as production, so all these tasks already take place there. Moreover, since betas have different Solid Queue instances, we can't prevent simultaneous runs of the same recurring jobs because each Solid Queue instance is isolated from the others, so they don't know these jobs are running already, leading to all sort of issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Betas use the same application DB as production, so all these tasks already take place there. Moreover, since betas have different Solid Queue instances, we can't prevent simultaneous runs of the same recurring jobs because each Solid Queue instance is isolated from the others, so they don't know these jobs are running already, leading to all sorts of issues.