Issue Resolution Bot
Playbooks for critical & high issues — recommend-only, human-approved, 0 tokens
Issues triaged
16
Needs co-browse
5
human Cowork session
Stale info
5
Resolved
1
fixed & retired
Learned patterns
4
Learned Auto-Fix Candidates
These issue types recur often enough that the bot proposes encoding their playbook as a dedicated deterministic helper (written to helper_backlog/, approve in Helper Discovery).
Deterministically apply the known playbook for recurring 'compliance-expiration' issues.
Deterministically apply the known playbook for recurring 'stale-connection' issues.
Deterministically apply the known playbook for recurring 'single-point-of-failure' issues.
Deterministically apply the known playbook for recurring 'activation-blocker' issues.
Escalation queue gap: escalations live only in Teams chat; no owned queue; 14-day FLOW R silence is invisible without a scheduled stale-task review
Resolution steps · owner: AI Operations Manager
- 1.Open the tenant admin (Power Automate / Power BI) in a human Cowork/co-browse session.
- 2.Locate the flagged connection and re-authenticate it (owner credential — human only).
- 3.Re-run the dependent flow's acceptance test; confirm a single Succeeded state.
- 4.Record the reauth + result in the Executive Decision Log (human).
Needs a live tenant/portal step — hand off to a human co-browse session. Nothing is auto-executed.
Zero active drivers at school-year start. Full pipeline is live but first activations are still pending; every territory is uncovered if routes are offered now
Resolution steps · owner: AI Operations Manager / AI Recruiter
- 1.Push in-flight drivers through the remaining activation gates.
- 2.Confirm acceptance detection is live; watch the acceptance mailbox.
- 3.Report per-territory coverage weekly to catch stalls.
Pipeline workbook is a single point of failure (single Excel workbook = system of record for the live pipeline)
Resolution steps · owner: AI COO
- 1.Document break-glass access for the single-owner resource.
- 2.Add a second delegate / monitored mailbox / backup owner when staffing allows.
- 3.Enable versioning + backup discipline on the system of record.
Column re-tokening across ~90 flow-written columns during Lists cutover. Excel connector keys rows by display name; SharePoint/Lists internal names differ (proven class: DL# → DLx0023). Every item()?['…'] token in every repointed flow — worst case FLOW R's 67-paren filter, which must be re-typed in chunks per SOP-02 (…
Resolution steps · owner: AI Automation Specialist
- 1.Assign a clear owner for this issue.
- 2.Define the single next action and a review date.
- 3.Track status until resolved; log the decision in the vault (human).
CST ongoing obligations unverified (GPS, Medical Card, quarterly MVR, annual background, safety meetings) — blocks renewal-tracker design and correct CC readiness claims
Resolution steps · owner: AI Compliance Officer
- 1.Pull the current document/record for the expiring item (human, source system).
- 2.Confirm the renewal date and required evidence.
- 3.Schedule the renewal and assign the owner; set a review date before expiry.
- 4.Update the Compliance Index / Requirements Matrix in the vault (human).
Needs a live tenant/portal step — hand off to a human co-browse session. Nothing is auto-executed.
Recruiting funnel thinness/staleness: ~42 leads were already stale at FLOW R enablement; re-engagement capacity is manual; no per-territory sourcing targets
Resolution steps · owner: AI Recruiter
- 1.Open the tenant admin (Power Automate / Power BI) in a human Cowork/co-browse session.
- 2.Locate the flagged connection and re-authenticate it (owner credential — human only).
- 3.Re-run the dependent flow's acceptance test; confirm a single Succeeded state.
- 4.Record the reauth + result in the Executive Decision Log (human).
Needs a live tenant/portal step — hand off to a human co-browse session. Nothing is auto-executed.
No ongoing-compliance layer while first routes approach. Expirations (license, insurance, clearances, drug/camera cadences) are not tracked post-activation; school year 2026-27 starts within weeks
Resolution steps · owner: AI Compliance Officer
- 1.Pull the current document/record for the expiring item (human, source system).
- 2.Confirm the renewal date and required evidence.
- 3.Schedule the renewal and assign the owner; set a review date before expiry.
- 4.Update the Compliance Index / Requirements Matrix in the vault (human).
Needs a live tenant/portal step — hand off to a human co-browse session. Nothing is auto-executed.
FLOW 08 Gates 2–3 never test-driven (broker-split drug test; completion+HandoffLog); flow ON with ≥1 real MI driver mid-vetting
Resolution steps · owner: AI Automation Specialist
- 1.Pull the current document/record for the expiring item (human, source system).
- 2.Confirm the renewal date and required evidence.
- 3.Schedule the renewal and assign the owner; set a review date before expiry.
- 4.Update the Compliance Index / Requirements Matrix in the vault (human).
Needs a live tenant/portal step — hand off to a human co-browse session. Nothing is auto-executed.
FLOW 11 acceptance auto-detection spec'd but build unconfirmed — contract acceptance likely still manual (GoKart Contract Accepted = Yes)
Resolution steps · owner: AI Automation Specialist
- 1.Assign a clear owner for this issue.
- 2.Define the single next action and a review date.
- 3.Track status until resolved; log the decision in the vault (human).
Single-owner account concentration (tjohnson@ mailbox monitored for acceptance; Automation@ posts; one admin)
Resolution steps · owner: AI Risk Manager
- 1.Document break-glass access for the single-owner resource.
- 2.Add a second delegate / monitored mailbox / backup owner when staffing allows.
- 3.Enable versioning + backup discipline on the system of record.
Pipeline Health Monitor Office Script #139 exclusions not applied — 3 false positives + A600 + test row in health digest (report-only)
Resolution steps · owner: Troye (Excel → Automate)
- 1.Assign a clear owner for this issue.
- 2.Define the single next action and a review date.
- 3.Track status until resolved; log the decision in the vault (human).
Automate@ consolidation collapses issuer≠executor segregation (DR-107/DR-050). Moving runtime + ownership onto one Automate@ service account means the same identity both issues and executes commands — the audit IssuedBy≠executor control and the "humans decide, only APPROVED enforces" separation weaken. Also two servic…
Resolution steps · owner: AI Risk Manager / Troye
- 1.Assign a clear owner for this issue.
- 2.Define the single next action and a review date.
- 3.Track status until resolved; log the decision in the vault (human).
Single-broker concentration: DE/VA/MD depend entirely on EverDriven, PA/FL on CST — a broker-relationship stall halts whole states
Resolution steps · owner: AI Broker Relations Manager
- 1.Assign a clear owner for this issue.
- 2.Define the single next action and a review date.
- 3.Track status until resolved; log the decision in the vault (human).
PAD robot (CC account creation) not built — CC provisioning stays manual
Resolution steps · owner: AI Automation Specialist
- 1.Assign a clear owner for this issue.
- 2.Define the single next action and a review date.
- 3.Track status until resolved; log the decision in the vault (human).
Orphan sweep (form submissions without pipeline rows) — possible lost leads
Resolution steps · owner: AI Recruiter
- 1.Assign a clear owner for this issue.
- 2.Define the single next action and a review date.
- 3.Track status until resolved; log the decision in the vault (human).
VA reimbursement-after-20-routes line copied DE-style — policy applicability unconfirmed
Resolution steps · owner: Troye (decision D-2)
- 1.Assign a clear owner for this issue.
- 2.Define the single next action and a review date.
- 3.Track status until resolved; log the decision in the vault (human).
Resolved (1)showhide
Fixed in the source systems and retired via config/resolved_issues.json — no longer counted as active or stale.
GK-Command-Router has a stale Power BI connection (CONFIRMED S066). Root cause confirmed by read-only tenant inspection 2026-08-06: the stale connection is GK-Automate-PowerBI (router R4) (Power BI, Automate@), status Reconnect, last modified 8/6 11:46:31 AM (the failed R4 run). SharePoint, Teams, and Outlook connecti…
Resolution note
Power BI connection GK-Automate-PowerBI (router R4) re-authenticated; dependent R4 flow re-run and confirmed Succeeded.
Vault Risk Register still marks this OPEN — recommend updating 15-Risk-Management/Risk Register.md to RESOLVED so the dashboard and the source of truth stay in sync. (Recommend-only — human edits the vault.)
recommend-only · cowork/co-browse steps need a human · vault read-only · 0 tokens