remove CAA mention in managed https doc#823
Merged
viniciusgiles merged 2 commits intomainfrom Feb 11, 2026
Merged
Conversation
✅ Deploy Preview for support-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
rafaelmatsumotomb
approved these changes
Feb 11, 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
2 participants
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.
CAA verification step is not necessary during troubleshooting.
Note
Low Risk
Documentation-only change that narrows troubleshooting steps; no product or runtime behavior is affected.
Overview
Updates the managed HTTPS troubleshooting guidance by removing the suggestion to check CAA records when a certificate is stuck in
Pending, leaving only DNS propagation and support escalation steps.Written by Cursor Bugbot for commit 405c508. This will update automatically on new commits. Configure here.