Add note about cronjob #4657
Merged
Add note about cronjob #4657
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
gclssvglx
approved these changes
May 17, 2024
|
Nice one! We can probably also stop these alerts from firing in Staging altogether 🤔 |
davidtrussler
deleted the
Update-section_Signon-API-user-token-expires-soon
branch
|
Now dropped from Staging, so we should consider revising this @davidtrussler 🙏 |
Cheers Chris, yes, I've passed that onto the next shift with an explanation of events. |
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.
This change adds a note to the "Signon API user token expires soon" section to the effect that any alerts relating to Staging (currently) and Integration (in the future) do not need any action. This is because the overnight cronjob updates the token in this environment to match any changes made in Production. The change is shown in the screenshot below.