Temporarily disable historical cache job #4073
Merged
Conversation
This file contains 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
cielf
approved these changes
Feb 1, 2024
|
It's OK to leave the env variable off for now on staging - we really only need to turn it on while doing testing. |
|
Should we go ahead with an off-schedule production deploy? |
|
@awwaiid Ehn. Not during business hours, certainly. I would consider it for tonight -- Do we have a sense of how long it will take to clear out the backlog of jobs? |
|
We should clear them out manually. I can put in a PR for this too. |
|
We'd just be clearing out the historicals, right? Leaving the email jobs? I think we are going to have some noise from the banks whichever way we go on that. |
|
Yep. |
|
@dorner: Your PR |
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.
See issue #4064 . This way it'll only run if the env variable is set.