Understand validation findings and Issues
Identify what a finding checks and make a focused correction.
Read the finding in context
Open Issues and inspect the exact message, affected resource or connection, and available details. A finding may concern service configuration, placement, a relationship, generated permissions, or export readiness. Follow its link to the relevant part of the design when offered.
Work through one cause at a time
- Identify the resource or relationship named in the finding.
- Review the relevant field, boundary, or connection.
- Make the smallest change that addresses the stated issue.
- Let the project save and review the updated findings.
- Create a new revision before comparing the next export result.
An unknown Region-availability result is not automatically a confirmed unsupported service. Preserve that distinction when reviewing an uncertain finding with your team.
Understand the limits of a pass
A successful check provides evidence for the checks that ran against that design or artifact. It does not guarantee production availability, security, cost, or suitability for every environment. Review package evidence and your own deployment requirements together.
Challenge a finding with evidence
Include the exact message or finding identifier, project and revision identifiers, resource configuration with sensitive values removed, and why you believe it should pass. Note whether the result appears in the editor, revision assessment, or generated package. These stages may describe different versions or different checks.
Include this guide and what you tried in your ticket so we can pick up from there.
Contact support