# Rovo agent missing after Rovo activation: Deployment required to restore functionality **URL:** \ **Category:** Rovo\ **Tags:** rovo-action, rovo-agent, rovo-activation\ **Created:** [December 3, 2024, 2:34pm UTC](https://community.developer.atlassian.com/t/rovo-agent-missing-after-rovo-activation-deployment-required-to-restore-functionality/86838 "2024-12-03T14:34:27Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![SvenHe](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/svenhe/32/43840_2.png) [@SvenHe](https://community.developer.atlassian.com/u/SvenHe)\ **Post date:** [December 3, 2024, 2:34pm UTC](https://community.developer.atlassian.com/t/rovo-agent-missing-after-rovo-activation-deployment-required-to-restore-functionality/86838/1 "2024-12-03T14:34:28Z")
Hi Community, I’ve come across an issue with Rovo while working on a Confluence app that includes a custom Rovo Agent. Here’s what I’ve observed: - If my app is installed _after_ Rovo is activated on a site, my custom agent becomes available immediately. ✅ - However, if Rovo is activated _after_ my app has already been installed, the custom agent does not appear for users. It’s completely missing from the browse agents dialog as well. ❌ The only way to resolve this is by redeploying my app, after which the agent becomes available. However, this workaround isn’t ideal, especially in production environments where seamless functionality is critical. Best regards, Sven ---
**Author:** ![dmorrow](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/dmorrow/32/35895_2.png) [@dmorrow](https://community.developer.atlassian.com/u/dmorrow)\ **Post date:** [December 3, 2024, 8:30pm UTC](https://community.developer.atlassian.com/t/rovo-agent-missing-after-rovo-activation-deployment-required-to-restore-functionality/86838/2 "2024-12-03T20:30:26Z")
Hi @SvenHe , Thank you for pointing this out. I’ve created an issue that you won’t be able to see, but the reference is [AIM-4200: Forge Rovo Agents are unavailable after activation of Rovo](https://product-fabric.atlassian.net/browse/AIM-4200). > The activation of Rovo for a site involves setting up the initial set of default Agents, but it appears this setup doesn’t take into account installed apps that provide Rovo modules. > > **Steps to reproduce** > > 1. Install a Forge app that includes a Rovo Agent module in a site for which Rovo is not already activated. > 2. Activate Rovo for the site. > 3. Observe the Agents available. > > **Expected result** > > At step 3, the set of available Agents includes the Agent provided by the Forge app. > > **Actual result** > > At step 3, the set of available Agents does not include the Agent provided by the Forge app. > > **Notes** > > Re-deploying the app after Rovo has been activated in a site will make the app’s Agent available, but this is not considered a viable workaround. Regards, Dugald ---
**Author:** ![SvenHe](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/svenhe/32/43840_2.png) [@SvenHe](https://community.developer.atlassian.com/u/SvenHe)\ **Post date:** [December 4, 2024, 1:26pm UTC](https://community.developer.atlassian.com/t/rovo-agent-missing-after-rovo-activation-deployment-required-to-restore-functionality/86838/3 "2024-12-04T13:26:02Z")
Thank you @dmorrow ! ---
**Author:** ![rafal.janiczak1](https://avatars.discourse-cdn.com/v4/letter/r/90ced4/32.png) [@rafal.janiczak1](https://community.developer.atlassian.com/u/rafal.janiczak1)\ **Post date:** [December 10, 2024, 4:03pm UTC](https://community.developer.atlassian.com/t/rovo-agent-missing-after-rovo-activation-deployment-required-to-restore-functionality/86838/4 "2024-12-10T16:03:00Z")
Hi I wanted to ask if you have an ETA for providing a fix for this bug? Regards, Rafał ---
**Author:** ![dmorrow](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/dmorrow/32/35895_2.png) [@dmorrow](https://community.developer.atlassian.com/u/dmorrow)\ **Post date:** [December 12, 2024, 9:34pm UTC](https://community.developer.atlassian.com/t/rovo-agent-missing-after-rovo-activation-deployment-required-to-restore-functionality/86838/5 "2024-12-12T21:34:07Z")
Hi @rafal.janiczak1 , There’s no estimate yet for when this will be fixed, but I’ll follow up with the team to see if it can be prioritised. Regards, Dugald ---
**Author:** ![sopel](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/sopel/32/48679_2.png) [@sopel](https://community.developer.atlassian.com/u/sopel)\ **Post date:** [September 21, 2026, 12:02pm UTC](https://community.developer.atlassian.com/t/rovo-agent-missing-after-rovo-activation-deployment-required-to-restore-functionality/86838/6 "2026-09-21T12:02:23Z")
Unfortunately this has seemingly still not been addressed, and given increasing Rovo adoption, it’s affecting an increasing number of partners and mutual customers. There’s now a public work item to track this significant oversight: - [Forge Rovo Agents are unavailable after activation of Rovo (ROVO-1239)](https://jira.atlassian.com/browse/ROVO-1239)