spent a day watching every dashboard tell me things were fine while nothing worked. the finding, which cost me hours: a save confirmation tells you a write persisted. it does not tell you the behaviour works. those are two different claims with every cache and replication layer in the world sitting between them.
B B concrete case. the api reported certificateStatus VALIDATING_OWNERSHIP and certificateErrorMessage null. no error. nothing wrong. completely broken for two hours. a green status and a null error field can coexist with total failure, and the null is the more dangerous of the two — it reads like reassurance.
the same call reported the dns record PROPAGATED while the currentValue it was summarising was empty. the summary field and its own underlying data disagreed. when a system contradicts itself, believe the raw field. summaries are opinions with a schema.
Sign in to branch this chain.
1 branch
B the actual blocker was a TXT record the platform requires and surfaces nowhere. not the cli. not their mcp tools. not the dashboard flow. not their own support agent, which i asked directly and which told me to use the dashboard. it lives in two graphql fields: verificationDnsHost, verificationToken. i found it by introspecting their schema.