Rovo Dev: Something went wrong on our end.

Question

Hello,

For about a week now, I've been trying to create a Rovo Dev webspace, but every time I get this error message:

Something went wrong on our end. Please try again. If this keeps happening, contact support. (Issue ID for Atlassian use: Trace ID: 876949e67a044546851471f4f2d61afe)

What gives?

Himanshu Tiwary_go407r · Answer

Hi @a40 ,

you should still be able to contact Atlassian Support even without the Rovo Dev webspace URL.

Just mention that the webspace is never created, so no URL is available, and include your Atlassian site URL, the exact error message, and the Trace ID

Since it has been failing consistently for a week, this still looks more like an Atlassian-side backend or feature-access issue than a local configuration problem.
Please Up-vote for this answer if it helps

a40 · Answer

I would love to contact Atlassian Support, but it seems impossible, due to the fact that I need to supply them with a Rovo Dev webspace / site URL, which I'm unable to obtain since it is never created.

Himanshu Tiwary_go407r · Answer

Hi @a40 ,

This looks more like an Atlassian-side issue than something you’re doing wrong.

The biggest clue is that you’re getting a Trace ID with the error. Usually that means the request is reaching Atlassian’s backend, but something is failing on their side when the Rovo Dev webspace is being created.

make sure Rovo Dev is actually enabled for your org/site

if this feature is still under beta / controlled rollout, confirm your site has been approved for it

try from another browser or an incognito window just to rule out a local session issue

But since you’ve been hitting the same error for about a week, I wouldn’t spend too long troubleshooting locally. At that point, the best next step is really to contact Atlassian Support and include the full error message plus the Trace ID:876949e67a044546851471f4f2d61afe

That should help them find the failed request in their logs much faster.

this is most likely either: a backend issue on Atlassian’s side, or a problem with feature access / rollout for your site

If this reply helped, I’d really appreciate a Kudos.