Administration

How Yavaren is doing

Yavaren's daily check of its own results, what it fixed by itself, and what needs you.

Yavaren checks its own results every day. It compares them with the week before and tells you what got worse.

What you see

Open How Yavaren is doing in the navigation. It shows these parts:

• Trends. Each measure has its value, the week before, and a small chart:
• the share of jobs that succeeded;
• the share of stories that passed their checks the first time;
• fix rounds per story;
• review findings per pull request;
• time to the pull request;
• time to merge;
• abandoned pull requests;
• engineer hours per story.

A measure with too few jobs says "too few" rather than guessing. - What got worse. A measure counts as worse only when the change is both large and unlikely to be chance. Next to it, Yavaren lists what changed in the same period: a new prompt version, an agent, a lesson it learned. Those are the first things to look at; they are not proof of the cause. - Fixed by itself. These jobs failed because of something outside the work, and a retry fixed them. Examples: a network interruption, a busy package registry, a runner that stopped. - Needs a person. These jobs failed because of the work itself or a setting, such as failing tests, an unclear story or a refused credential. Each shows what went wrong and what to do next. - What Yavaren learned. The lessons it formed from your own work, with a link to the full list.

What Yavaren does on its own, and what it never does

• It retries only failures of the infrastructure around the work. It waits before each retry, adjusts how it runs (for example a longer time limit), and stops after a small number of tries. Each retry is in your activity log.
• It never retries a failure of the work itself. A person decides what happens next, for example by refining the story and requeuing the job.
• It never merges, approves or pushes to your main branch, and it never skips an approval you asked for.

Your choices

An admin can switch automatic retries off. An admin can also allow a retry after an agent's rate limit or time-out to use another agent; this applies only to engineers on Yavaren's licence. Admins choose whether they get an e-mail when a result gets worse, or when the same failure keeps happening. A member can run a check now, and can cancel a retry that is still waiting.