[DOCS-14475] Document ~24h delay before new Agent versions appear in Fleet#36908
Open
oleroydatadog wants to merge 1 commit into
Open
[DOCS-14475] Document ~24h delay before new Agent versions appear in Fleet#36908oleroydatadog wants to merge 1 commit into
oleroydatadog wants to merge 1 commit into
Conversation
…Fleet Signed-off-by: Olivier Leroy <olivier.leroy@datadoghq.com>
Contributor
Preview links (active after the
|
fb97779 to
5e14e91
Compare
janine-c
approved these changes
May 21, 2026
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
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.
What does this PR do? What is the motivation?
Fixes DOCS-14475
Adds a Troubleshooting entry to the Upgrade Agents page noting that a newly released Agent version can take up to 24 hours before it appears as an upgrade target in Fleet Automation. Customers occasionally report the latest version is missing from the upgrade picker shortly after release; this entry lets them self-serve before contacting support.
Merge instructions
Merge readiness:
Additional notes