Relationships
#640 reports.require in workflow YAML does not auto-execute pulled extension reports
Opened by mellens · 6/12/2026· Shipped 6/13/2026
Description
reports.require in a workflow YAML file does not cause a pulled extension report to execute automatically. The bundle is present on disk, the name matches exactly, but the report is silently skipped. Passing --report <name> explicitly on the CLI does cause the same report to execute successfully.
Steps to reproduce
- Pull a report extension:
swamp extension pull @webframp/aws/terraform-drift - Confirm the bundle is built:
ls .swamp/report-bundles/— thedrift_report.jsbundle appears - Create or use an existing workflow YAML with:
reports: require: - "@webframp/terraform-drift-report"
- Run the workflow:
swamp workflow run my-workflow - Expected: the
@webframp/terraform-drift-reportreport runs and writes areport-webframp-terraform-drift-reportdata artifact - Actual: the report does not run.
swamp report searchreturns zero results for this report. No error or warning is emitted. - Workaround:
swamp workflow run my-workflow --report @webframp/terraform-drift-report— this triggers the report correctly
Key observation
A local extension report (extensions/reports/my_report.ts) declared in reports.require does auto-execute correctly. The failure is specific to pulled extension reports.
Environment
- swamp:
20260609.232501.0-sha.873563f2 - OS:
darwin - Extension:
@webframp/aws/terraform-drift@2026.05.24.1(bundle confirmed present in.swamp/report-bundles/) - Report name in extension source:
@webframp/terraform-drift-report(verified matchesrequireentry exactly)
Shipped
Click a lifecycle step above to view its details.
keeb commented 6/12/2026, 11:56:04 PM
Thanks for the detailed report, @mellens. We could not reproduce the silent skip on Linux — at your exact build (873563f2) and at HEAD, a pulled @webframp/aws/terraform-drift report auto-executes via reports.require on both cold and warm catalog runs. A fix is in progress regardless that makes every path here loud: an unresolvable required report now logs a warning, emits report_failed, writes a searchable error artifact (so swamp report search shows it), and fails the run; workflow resume (which silently skipped ALL reports) now runs them.
To pin down what broke on your machine, could you share:
- Catalog state for reports:
sqlite3 .swamp/_extension_catalog.db "SELECT type_normalized, state, last_error FROM bundle_types WHERE kind='report'" - A failing run with debug logs:
swamp workflow run <your-workflow> --log-level debug(the report-loader and catalog lines especially) - Whether the failing runs were plain
swamp workflow run, resumed runs (swamp workflow resume), or scheduled viaswamp serve
One detail that would help: --report is a pure narrowing filter over the same candidate set as require, so for it to run the report while require alone skipped it, the repo state must have changed between those two runs — e.g. the extension pull in your repro steps may have repaired a broken catalog entry. If you can still reproduce the silent skip today, the three items above should name the culprit immediately.
Sign in to post a ripple.