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

Scenario Troubles

Mike Stone

I have an agent that has two scenarios that sometimes execute instructions from both scenarios in one session when it should only be executing the instructions for one scenario.

Debugging a bit more, it appears it switches out of the correct scenario into the other scenario and merges.

Accepted answers

Ryan Boyd

What are the triggers and scenarios? if you can share.

All comments

Ryan Boyd

What are the triggers and scenarios? if you can share.

Mike Stone

The agent assists with investment requests.

Scenario A is for internally funded requests. This is the default scenario.
Scenario B is for customer funded requests.

The user is presented with two conversation starters:

I have an internal R&D and/or product investment request.

I have a customer SOW/PWS deliverable I need development assistance with.

Scenario B trigger instructions:

Trigger this scenario when a user has a request for their customer and has a PWS or SOW.

## Positive examples:
This is a customer request or need.
There is a PWS or SOW.

## Negative examples:
This is an internal investment request.
This is a product or R&D request.

Mike Stone

What appears to happen is the user selects the conversation starter below and the agent executions instructions correctly for Scenario B.

I have a customer SOW/PWS deliverable I need development assistance with.

When the agent gets near the end of those instructions it then starts executing Scenario A instructions when it should finish and submit the request instead which are the last instructions for Scenario B.

Ryan Boyd

Ah. What do the debug logs say for that one?

Welcome!

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

Quick Links

Find more posts tagged with

rovo-atlassian-intelligence