Subject: Urgent: Technical Provisioning Failure / Trace ID Error during Site Creation To: Atlassian Technical Support / Site Administration Team Description of Issue: I am writing to report a persistent error encountered during the Atlassian site creation process. The system consistently fails to provision new sites, returning a standard "Something went wrong on our end" error message. This appears to be a server-side interruption in the site initialization workflow. Error Message Received: "Something went wrong on our end. Please try again. If this keeps happening, contact support." Technical Identifiers (Trace IDs): * Primary Trace ID: bdf74602dd9b43b19a501f3717969f7f * Secondary Trace ID: 1545887eee744dfb8800b7a06ca28e30 Observed Behavior: * User submits a unique, available site name. * The initialization process begins but terminates before completion. * The system returns the Trace IDs listed above. * Subsequent attempts frequently redirect to billing selection pages, suggesting the automated free-tier/trial provisioning logic is failing to trigger correctly. Environment Details: * Browser: Verified across multiple modern browsers (Chrome, Edge). * Account Status: New site registration. Requested Action: Please review the provided Trace IDs to determine the cause of this provisioning failure. If this is a known global issue or a regional service degradation affecting site creation, please provide an update on the resolution status. Regards, Site Administrator

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Urgent: Technical Provisioning Failure / Trace ID Error during Site Creation rovo

created 5th

Subject: Urgent: Technical Provisioning Failure / Trace ID Error during Site Creation

To: Atlassian Technical Support / Site Administration Team

Description of Issue: I am writing to report a persistent error encountered during the Atlassian site creation process. The system consistently fails to provision new sites, returning a standard "Something went wrong on our end" error message. This appears to be a server-side interruption in the site initialization workflow.

Error Message Received:

"Something went wrong on our end. Please try again. If this keeps happening, contact support."

Technical Identifiers (Trace IDs):

Primary Trace ID: bdf74602dd9b43b19a501f3717969f7f
Secondary Trace ID: 1545887eee744dfb8800b7a06ca28e30

Observed Behavior:

User submits a unique, available site name.
The initialization process begins but terminates before completion.
The system returns the Trace IDs listed above.
Subsequent attempts frequently redirect to billing selection pages, suggesting the automated free-tier/trial provisioning logic is failing to trigger correctly.

Environment Details:

Browser: Verified across multiple modern browsers (Chrome, Edge).
Account Status: New site registration.

Requested Action: Please review the provided Trace IDs to determine the cause of this provisioning failure. If this is a known global issue or a regional service degradation affecting site creation, please provide an update on the resolution status.

Regards, Site Administrator

Accepted answers

Florian Bonniec

Hi @created 5th

Please, raise a request to Atlassian support directly.

https://support.atlassian.com/contact/#/

Regards

All comments

Florian Bonniec

Hi @created 5th

Please, raise a request to Atlassian support directly.

https://support.atlassian.com/contact/#/

Regards

Dr Valeri Colon (Connect Centric)

Thanks @Florian Bonniec and welcome to the community @created 5th This is the right approach—Trace ID errors like this are backend provisioning failures, so only Atlassian support can investigate them. One thing to add: sometimes the site actually gets created despite the error, so check your email and existing sites first. If not, include your Trace IDs and account details in the support ticket so they can trace the failure quickly.

Francisco Marangoni

Thank you for the guidance. However, I am unable to submit a support ticket through the Atlassian support page because the form requires the URL of the affected site.

In this case, the site URL does not exist yet, since the issue occurs during the site creation and provisioning process itself. Therefore, I cannot complete the required field or proceed with the support request.

Is there an alternative support channel for provisioning issues where no site URL has been created yet?