Skip to content

Fix daily firewall report caching stale aggregated data #10492

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Mossaka merged 4 commits into from
Jan 17, 2026
Merged

Fix daily firewall report caching stale aggregated data #10492

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4276f0d
Initial plan
Copilot Jan 17, 2026
f52f72a
Initial plan for fixing daily firewall report caching issue
Copilot Jan 17, 2026
751ed0c
Fix daily firewall report caching to always fetch fresh data
Copilot Jan 17, 2026
386cd6e
Merge branch 'main' into copilot/fix-firewall-report-issue
Mossaka Jan 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions .github/workflows/daily-firewall-report.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

5 changes: 2 additions & 3 deletions .github/workflows/daily-firewall-report.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,13 +173,12 @@ Simply call the MCP tools directly as described in the steps below. If you want
2. If a report exists from the last 24 hours:
- Read the cached run IDs that were analyzed
- Determine if any new workflow runs have occurred since then
- If no new runs, update the existing report with current timestamp and exit early
- If no new runs, skip to Step 5 (Generate Report) using the same cached run IDs, but **always re-fetch fresh data from the audit tool** for accurate counts
3. Store the following in repo memory for the next run:
- Last analysis timestamp
- List of run IDs analyzed
- Aggregated blocked domains data

This prevents unnecessary re-analysis of the same data and significantly reduces token usage.
**IMPORTANT**: Never cache or reuse aggregated statistics (blocked counts, allowed counts, domain lists). Always compute these fresh from the audit tool to ensure accurate reporting. Only cache run IDs to avoid re-discovering the same workflow runs.

### Step 1: Collect Recent Firewall-Enabled Workflow Runs

Expand Down
Loading