Repository navigation
mention the request id echo when contacting support - #240
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
![graphify-labs-staging[bot]](https://avatars.githubusercontent.com/in/4517131?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found by static checks — no coupling regressions or blocking issues in the code graph. That is not the same as safe to merge: see what was not checked.
Not checked: tests were not run; no formal proof of the changed code.
Graphify review — findings
Documents X-Request-Id header handling so clients can supply a 1–128 character value that Graphify echoes on responses except for publicly cached /.well-known/* paths. Support pages now instruct users to include both the echoed X-Request-Id and the existing correlationId or X-Correlation-ID when filing issues. Cross-origin browser callers cannot use the header.
No blocking issues surfaced. 2 lower-confidence candidates did not survive cross-model review.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 45 functions depend on the 45 functions this change touches.
Health — grade A; no new coupling hotspots.
Verification — 45 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 45 function(s) in the blast radius were not formally verified this run
If your client sends an X-Request-Id header, Graphify echoes it on the response, except on publicly cached paths such as /.well-known/*. The header has a short allowed format and does not replace correlationId or X-Correlation-ID. Troubleshooting, rate limits, and the FAQs now ask you to include it when you contact support if you have it.