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; } } }

Forge deploy fails for Rovo Agent when I update prompt

Steve S_

I create a new Rovo agent.

I can deploy and install it.

If I update the prompt the cli command forge deploy fails:

Error: Manifest validation failed: Agent not allowed
Additional information: {
"agents": [
"name-agent"
]
} (requestId: xxxxxxxxxxxxxxxxxxxxx)

If I put back the original prompt instructions the cli command forge deploy works.

Why would updating the prompt break the ability to do a deployment?

Accepted answers

Akash Singh_vujl0e

@Steve S_ Have you embedded your prompt inside the manifest file itself? If yes, then it could be a possibility that the prompt is invalidating the yaml indentation or semantics. I would highly recommend you to move the entire prompt content to a text file and place it separately within your app.

Read this Atlassian guide on how to do it.

All comments

Akhand Pratap Singh_z78moi

Hello @Steve S_ ,

Good day, Welcome to Atlassian Community!!

Because you have once deployed and installed your ROVO agent that agent name is now registered, try updating your ROVO agent name from "name-agent" to some other and then try to redeploy

Steve S_

I am not trying to create a duplicate of the existing agent, simply update the agent with additional prompt instructions. Additionally, I can re-deploy as much as I want with the same name as long as I don't update the prompt section. That said...

I did as you recommended and change the name, and it still failed.

Are there additional steps one must take when updating the prompt instructions area of the manifest file before a deploy?

Akash Singh_vujl0e

Read this Atlassian guide on how to do it.

Steve S_

I appreciate the suggestion, and now I know how to use a relative path!

But alas, it now fails with a new error, "Error: Manifest validation failed: Agent not allowed".

Since it no longer references the agent-name as the issue, I decided to update the prompt command completely with something very vanilla like, "you are a change manager, and your purpose is to provide guidance about change procedures..." and it deployed without an issue.

...would Atlassian block certain vocabulary? Is there a no-no list of words not allowed?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management