Agentic Workflow Audit — 2026-03-11 (Run #233) #20474
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-03-12T05:49:52.304Z.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Daily audit of agentic workflows as of 2026-03-11. This is the first audit run (#233) establishing baseline metrics. Note: the
logsMCP tool was unavailable (gh CLI not authenticated), so detailed per-run metrics (token usage, cost, errors) could not be collected. Analysis is based on workflow status only.Summary
Engine Distribution
Active Workflows (35)
View all active workflows
Issues Found
Two workflows have exceeded their
stop-afterdeadline and are marked Expired:ci-doctor— triggers onworkflow_run(CI completes),stop-after: +1modaily-team-status— daily schedule,stop-after: +1moThese workflows should be reviewed and either renewed (update
stop-after) or disabled if no longer needed.The
logsMCP tool failed withexit status 1(gh CLI not authenticated). This prevented:This is a recurring infrastructure constraint for this audit workflow. Future runs will benefit if gh CLI authentication is available.
ℹ️ Repo Memory Bootstrap Issue
This is the first audit run — no historical baseline exists in repo memory. The
push_repo_memoryvalidation reported an oversized diff (~26–27 KB) due to git pack format overhead when initializing a new branch for the first time. Historical comparison will become available in subsequent runs.Observations
Unknownstatus — this is expected for event-triggered workflows (slash commands, PR labels, reactions) that haven't run recently or are disabled.compiled: Yesfor all 166).Recommendations
ci-doctoranddaily-team-status— both have expiredstop-afterlimitsReferences:
Beta Was this translation helpful? Give feedback.
All reactions