Help centre · Troubleshooting
What happens when a run asks for clarification?
Why the agent stops to ask, where to answer, and how to stop it happening again.
When the agent reading the issue meets an ambiguity that would change the code it writes, it stops and asks instead of guessing. The run moves to awaiting input, a question is posted on the issue, and the pipeline resumes as soon as you answer.
Why does it not just guess?
Because guessing costs more than asking. An issue saying "add an export" without saying in what format leads to a full run, a merge request, a review — and work to redo. Thirty seconds of answer avoids all of it.
Where do I answer?
Two places, your choice:
- In Diavi, from the waiting run: a form lists the questions. This is the fastest route, and your answer is also posted on the issue so your team sees it.
- On the issue itself, as a comment.
What happens after I answer?
A new run starts with your answer in context. It counts against your monthly allowance: it is a full execution of the pipeline, not a mid-way resume.
How do I stop it happening again?
Two levers, and the second pays off more:
- Write issues in terms of observable results rather than intent.
- If the same question keeps coming back — which export format, which naming convention, which library to use — that is not an issue problem, it is a missing convention. Write it once in Your contexts and no run will ask again.
What if I never answer?
The run stays waiting and consumes nothing further. You can cancel it at any time.