Problems and what to do

Messages you may see on the AEGIS pages.

The page says the service couldn't be reached, or the first action is slow.

The service scales to zero between visits and is starting.

Wait about 15 seconds and try again.

The sandbox has used its 20 proposals for today.

Record a decision for the gap instead, or try again tomorrow.

Every topic shows not approved.

Read the reason on each finding.

A topic whose last change was pushed directly, not merged through a reviewed pull request, fails check_approval until a reviewed change merges.

On the generate page, Approvals read 0 appears and the approval metrics show 0.

Merge the review pull requests in dita-corpus.

AEGIS trusts Git for approval. Until a change to each evidence topic merges through a pull request approved by a code owner, no topic counts as approved. The page reports this honestly. It isn't an error.

The metric for authority content in downstream output says not measured.

Check that the service has the DITA-OT output.

The scan needs the built HTML for both packs. Without it the metric can't run. It also isn't reported as a pass unless the control search on the authority pack finds the content.

After a download, the message says the manifest hash differs from the one shown.

Select Generate packs again, then download.

This can happen if the service restarted onto a new corpus commit between the two steps.