Why Did Rovo Archive My Confluence Page Instead of Reformatting It? [Champions Slack Insider]

[#1]

This thread sparked by @Darryl Lee is one of those moments that makes you pause

“I asked Rovo to reformat a page… and it archived it.”

Not partially updated. Not formatted incorrectly. Archived.

What actually happened

The flow was simple:

• User asks Rovo to reformat a page
• Rovo suggests a table format
• User refines: “Two tables are better”
• Rovo responds with an action prompt
• User confirms

Result: The page gets archived.

Why this happens

Short Answer: The model misinterpreted the intent and mapped it to the wrong action, and the UI did not clearly communicate what that action actually was.

Rovo is doing two things at once:

• Interpreting natural language
• Mapping that intent to a system action

In this case:

• “Reformat” should map to a content edit
• Instead, it mapped to an archive action

That alone is an issue, but the bigger problem is how it was surfaced.

The real issue is not just the action—it’s the clarity

Several patterns showed up here that are increasingly common:

• Actions labeled vaguely (e.g., “action…”)
• The proposed action does not clearly match the user’s request
• The confirmation step does not make the impact obvious
• The system proceeds after confirmation, even if the intent was misunderstood

So while confirmation did happen, it was not meaningful confirmation.

Why this matters

This is not just a formatting issue. It is a trust issue.

When users:

• cannot clearly see what action will be taken
• cannot verify that it matches their intent

they are effectively approving blind.

That creates risk, especially in environments where actions can:

• modify pages
• update tickets
• change system state

Is this a one-off?

No, this aligns with broader patterns seen in Rovo today.

Reported behaviors include:

• Incorrect actions being suggested for a request
• Vague or incomplete action descriptions
• Mismatches between user intent and system execution
• Unexpected updates after confirmation

This is part of a broader gap in action clarity and safety, not an isolated incident.

What should you do right now

If you are using Rovo for actions in Confluence or Jira:

• Read the action prompt carefully before confirming
• Be cautious with vague labels like “action…”
• When possible, test in low-risk environments first
• Capture screenshots and timestamps if something unexpected happens
• Report it through a support ticket

For high-impact actions:

• Consider using native tools or Automation instead

Champion takeaway

Rovo is powerful, but action execution is still maturing.

If the system clearly showed:

• what action will happen
• what object will be affected
• what the result will be

this situation would likely have been avoided.

Until then, the safest approach is to treat confirmations as high-stakes, even when the request feels simple.