HELP ME ! Paid Rovo Dev Subscription Not Recognized in CLI — Invoice & Group Config Confirmed

[Andrea Daniels]

[Dr Valeri Colon _Connect Centric_]

@Andrea Daniels welcome to the community. This usually comes down to entitlement sync, not billing. Your screenshots show Standard + invoice, but also 0 users assigned, which means the license isn’t actually applied to your account.

Make sure:

• You’re in the rovo-dev-agents-users group
• The site shows >0 licensed users
• You’ve re-logged into CLI

If it still fails, it’s a backend entitlement issue—support needs to refresh it.

https://support.atlassian.com/rovo/docs/add-rovo-dev-standard-to-your-site/

[Andrea Daniels]

Everything looks correct on our end, yet the CLI still prompts for a subscription. At this point, I believe this may be a product bug — the entitlement sync is failing silently even when all conditions are met. Has anyone else encountered this?

[Andrea Daniels]

To be more specific about what I believe is happening: when a paid plan is activated during or after a trial period, Rovo Dev's subscription entitlement is NOT properly synced to the site users — even when all permissions and group assignments are correctly configured. I have paid multiple times and the result is always the same. This is clearly a billing-to-entitlement sync bug on Atlassian's side.

I am extremely disappointed. I've done everything right, followed every instruction, and yet I still cannot use a product I've paid for. I have received no meaningful help so far. This needs to be escalated to the engineering team immediately — not just a link to documentation I've already read.

[Dr Valeri Colon _Connect Centric_]

@Andrea Daniels Your frustration makes sense—this one isn’t something the community can fully resolve.

You’re currently in the Atlassian Community (peer support), not direct Atlassian Support. I did flag your post using the “Request support” option, so it’s now in their queue.

If you want to contact them directly for faster handling:

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

Choose Billing, licensing & accounts → Rovo Dev and include your entitlement number and screenshots.

[Arkadiusz Wroblewski]

Hello and welcome to the Community @Andrea Daniels 

from your screenshots, this really does not look like a payment problem.

The part that stands out much more is that your setup still looks incomplete. Your user still shows as Invited, one screen still shows Quantity 0, and another still still shows the trial label. So even if the invoice was paid, the CLI can still behave as if the paid entitlement is not active for your user yet.

I would sort that part out first. Make sure the invited account is fully accepted and shows as active, then log out of the CLI and authenticate again.

If it still says the same thing after that, and the admin screens still keep showing 0 users or trial, then this starts looking much more like an Atlassian entitlement sync issue than anything wrong with your payment.

[Andrea Daniels]

Thank you for the detailed response — I really appreciate it.

Regarding your suggestion to make sure the invited account is fully accepted and active: I can confirm this 100%. The only user on this site is myself, and I am the admin. There is no separate "invited" account pending acceptance — it's just me.

Here's where things get confusing and I think this is the core of the issue:

- The Rovo Dev subscription (Standard plan, active/paid) is not a site itself — it has no URL. It is the subscription layer that contains my site as an linked application.
- The paid plan was activated from within this subscription, and my site appears there as the connected app.
- However, the licensed user count on the site level still shows 0 — even though in the Admin homepage and in the group settings, my user account is clearly listed and assigned.

So the admin panel and group configuration both recognize me as a user, but the site-level license count still shows 0. This is the exact contradiction I cannot explain — and I believe this inconsistency is what's causing the CLI to treat my account as unsubscribed.

This doesn't feel like a setup issue anymore. It looks like the entitlement is simply not propagating from the subscription layer down to the site level, despite everything being correctly configured.

[Andrea Daniels]