Troubleshooting Privacy Center Publishing and Custom Domains
Fix Privacy Center changes that are not live after a publish, a browser that still shows a draft, and domain or certificate errors.
After you read this page, you can find out why a publish is not live. You can also leave draft mode and fix domain or certificate errors.
Changes are not live after you publish
Check these causes in order:
- The publish is still in delivery. A background job delivers published changes every five minutes. Wait five minutes, then reload.
- Your browser is in draft mode. See Your browser still shows a draft.
- You selected Publish Messages Only. It publishes the Messages module and leaves other draft changes unpublished. Open Review & Publish and select Set Privacy Center Live.
- The draft matches the published version. Set Privacy Center Live is then unavailable, and each tab says "No changes detected". Refresh the page and open Review & Publish again.
Review & Publish can also show these errors:
| Message | Cause | Fix |
|---|---|---|
| "Timed out loading Privacy Center version data." | The modal could not load a version after two retries | Close the modal and open Review & Publish again |
| "Draft modules have not been saved" | Publish Messages Only found no saved draft | Select Save Changes, then publish |
| Your Privacy Center has never been published | Publish Messages Only needs one full publish first | Select Set Privacy Center Live |
| Draft module content is missing | Transcend could not find the saved draft content of the named module | Publish again. Contact Transcend Support if it repeats |
Any other publish error shows "Encountered unexpected error when setting changes to your Privacy Center live."
Your browser still shows a draft
Preview Changes turns on draft mode in your browser. Your Privacy Center then shows the banner "You are viewing a draft version of the Privacy Center". Draft mode shows your saved draft, so the page can differ from what visitors see.
To leave draft mode, select View Live on the banner, or View Live Privacy Center in the Admin Dashboard. Draft mode also ends two days after your last draft visit. Draft mode is stored in your browser, so it does not affect visitors.
Domain and certificate errors
Launch or Move Your Privacy Center Domain covers failed DNS validation, a locked switch, a hostname in use, and the attempt limit. This table covers the rest.
| Symptom | Cause | Fix |
|---|---|---|
| The badge stays on Setting up | Three checks must pass. AWS issued the certificate, the distribution is deployed, and your hostname returns your Privacy Center | Check the validation record and the routing record, then select Check status |
| "No CAA records found that allow AWS to issue certificates" | The CAA records on your root domain do not allow AWS | Add a CAA record for amazon.com, amazontrust.com, awstrust.com or amazonaws.com, then request again |
| "is not a valid domain" | Transcend could not parse the hostname as a domain | Enter the full hostname, such as privacy.example.com |
| A move shows Failed | AWS will not issue the certificate, or another CloudFront distribution already uses the new hostname | Fix the cause, then select Start over |
| The page returns to "Both domains are live." after you remove the old domain | AWS did not issue the certificate for the new hostname alone. Both domains still work | Select Remove old domain again |
| Request forms and downloads fail after you turn on Cloudflare proxying | Cloudflare challenges background requests, and browsers cannot complete a challenge | Skip challenges for POST requests to /privacy/graphql |
AWS can time out a certificate that does not validate within 72 hours. The Deployment tab then shows "DNS validation failed."