'URL No Longer Exists' when accessing a Community in recently refreshed Sandbox.
Last updated 2017-06-10 ·Reference W-2848555 ·Reported By 62 users
There is a potential issue where the domain records are left in place after a sandbox refresh. This causes problems after a refresh has taken place since two domain records from different org ids will resolve to one domain.
For Communities which use templates, this will cause a 'URL No Longer Exists' error when accessing that Community in the Sandbox.
Note: This is an intermittent behavior and does not happen with all sandbox refreshes.
1. In Production, enable Communities
2. Create a Sandbox. Ensure Communities work as expected in that SB.
3. Refresh the Sandbox. Communities in the new sandbox copy might exhibit the error noted above.
Log a case with Support to verify the cause of the error. If the error is in fact caused by this issue, Support can change the Community Subdomain for the affected sandbox as a workaround.
***IMPORTANT NOTE*** : This known issue is not the only possible cause of a 'URL No Longer Exists' error when accessing a Community in the Sandbox. That message can also appear if the Community needs to be published. Please open the Community Builder for the affected Community, click "Publish", wait for publish to complete, and confirm the error still happens before contacting Support for assistance.
Reported By (62)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.