Rovodev bugs

[ElEscarabajo]

I literally upgraded to the premium plan, but I can't use it. Then, after about 9 days or so, a friend told me that after that point, you can't use any IA models anymore. This is my site: https://cristoferpayamps206.atlassian.net/rovodev/site-settings. I literally can't use the Opus templates because "I don't have a premium plan."

> a
─── Model not available for current subscription ───────────────────────────────────────────────────────────────────────

The current model is only available with a paid Rovo Dev subscription. Please upgrade your subscription to access this
model.

──────────────────────────────────────────────────────────────────────────────────────────────────── ────────────────────
─── Using fallback model ────────────────────────────────── ─────────────────────────────────────────────────────────────

Model request failed after multiple attempts, trying fallback model.

──────────────────────────────────────────────────────────────────────────────────────────────────── ───────────────────

It's too tedious to pay and then find out the models don't work because you don't have a premium subscription 

[Dr Valeri Colon _Connect Centric_]

Hi @ElEscarabajo this usually isn’t a “bug,” but an entitlement or provisioning mismatch. Common causes:

• Subscription is active, but entitlements haven’t propagated yet
• You’re on Premium, but not assigned access to Rovo Dev features
• Wrong site/account authenticated in CLI or UI

Also, there’s no known “9-day cutoff”—that’s likely confusion with trial/credits. What to do:

• Check admin.atlassian.com → Billing + Product access
• Re-authenticate to the correct site
• If it persists → Atlassian Support (they often need to fix backend entitlements)