Relationships
#4464 Dashboard cannot show a step's log once the step's behavior definition is deleted, though the log data remains
Opened by zack · 11/5/2026· Shipped 11/5/2026
Description
When a run's behavior definition has been deleted, the dashboard's run view cannot show that step's log, even though the log data is still in the datastore. The step panel shows:
The step's log could not be loaded (Behavior not found: review-comments-cb586fdc-3919-4db5-95a5-df200f59c514).
This happens for every finished run of a workflow that uses per-run, ephemeral behaviors and deletes their definitions afterwards. verification/workflow-verify-reviews.yaml is one example: its steps run behaviors named review-*-${{ run.id }}, and the cleanup job deletes .swamp/auto-definitions/*-<run.id>.yaml.
Cause
packages/dashboard/src/components/StepLog.tsxfinds the log artifact in the run record, then asks for it withdata.getusingmodelIdOrName: ref.tags.modelName, plusdataNameandversion.- The serve
data.getpath resolves the behavior name first, throughservedModelResolverinsrc/serve/handlers/data_handlers.ts, which callsfindDefinitionByIdOrName. The definition is gone, so it throwsUserError("Behavior not found: <name>")and never reads the data. - The data is still there.
swamp data query 'tags.workflowRunId == "<run>" && tags.step == "<step>"'returns the step'sresultandlogitems. The run record also already holds each artifact'sdataId.
Expected
The dashboard shows a step's log for any run whose data is still stored, whether or not the behavior that wrote it still exists. One approach: let the step log read the artifact by the dataId (or run, job and step) recorded in the run, rather than resolving the behavior name first. Authorization needs care. Today a read is authorized against the behavior's resource, so a deleted definition needs a defined answer. The workflow's owners, or the not-found-by-name treatment that is already used, could fill that role without telling a caller anything about data they may not read.
Steps to reproduce
- Run a workflow whose step uses a per-run behavior, and delete that behavior's definition after the run (e.g.
verify-reviews, whose cleanup job does this). - Start
swamp serveand open the dashboard on that run. - Select any step. The log panel shows "The step's log could not be loaded (Behavior not found: …)".
swamp data querywith the run's tags still returns the log and result items.
Environment
- swamp 20261105.192430.0-sha.2d08404e, Linux
- Example run:
verify-reviewsruncb586fdc-3919-4db5-95a5-df200f59c514
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.