Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to enforce a custom Rovo agent to search for TECH Document information for a legacy job?

Narmatha A
August 2, 2026

I have created a Custom ROVO agent . Purpose of the agent is if tidal job is an input means response should return all the informatica components if exist and suc/TDD documents confluence link .

scenario1:
If TDD link doesn’t exist for a legacy job it should check all jira stories does anything have this tidal job mentioned and return the link . General Agent is able to track it but my custom agent not doing it.

scenario 2:

There is another scenario even everything all exist . It is returning java TDD,Azure TDD links not associated with my tidal job or infa component. 

Scenario 3 : Similar to Scenario 2 tried different job it had all details accurate but returned different job informatica components 

1 answer

0 votes
Viswanathan Ramachandran
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 2, 2026

Hi @Narmatha A 

For scenario 1

Root Cause: Custom agents do not perform fallback multi-step searches unless explicitly commanded in the system instructions. 
Solution: Define an explicit Fallback Execution Chain and explicitly enable your search tool in your Agent settings.

For scenario 2

Root Cause: Rovo uses semantic similarity search. If a direct exact match for your Tidal job is weak, the vector search returns generic technical documents (like Java/Azure TDDs) because they contain similar words (e.g., "TDD", "Job", "Pipeline").
Solution: Enforce Exact String Matching and strict Relevance Filtering in the instructions.

For scenario 3

Root Cause: The agent is retrieving the correct details but its extraction context window is pulling Informatica component names from neighbouring tables, templates, or related sections within the same space.
Solution: Bound the Data Extraction Scope within your prompt instructions.

This checklist below might help

Field Recommended Action
Knowledge Attach specific space/project where Tidal/Informatica details live.
Tools Ensure both Search tools are attached.
Instructions Implement strict string matching, fallback execution steps, and extraction boundary rules.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events