Workflows & Self-Service
Workflow Failures
When a GitHub Actions run fails or times out, CodeCargo explains why. The explanation shows on that workflow in the Workflows inventory, and on the failed attempt in the workflow's Runs tab. It appears about a minute after the run finishes.
The explanation names the likely cause, the job and step that failed, whether a re-run is likely to pass, and whether the fix is in the repository. If the same failure has already happened, it says so. A later attempt of that run that passes is shown as flaky, even if the first explanation expected the failure to stick.
The Troubleshoot assistant on the run starts from this explanation. The assistant in the GenAI Editor can read it too when you ask about the run. When the same failure keeps happening, CodeCargo can notify you — manage that with your other notifications.
When you don't see an explanation
Explanations are available on plans that include CodeCargo-managed AI. A bring-your-own-key (BYOK) plan does not receive them. Cancelled runs are not explained. CodeCargo only adds an explanation if the run finished within the last day and does not have one yet. A burst of failures can take longer than a minute. Contact your CodeCargo administrator if you expect explanations and never see them.
CargoWall
An explanation attributes the failure to CargoWall only when CargoWall blocked a connection while enforcing in the failed job, and the failure also looks like a connection or dependency problem — or the failure text names a host that was blocked. A block in audit mode, or a block that does not show up in the failure, is not reported as the cause. When CargoWall is the cause, the explanation names the blocked host.