Repository navigation
API-created workflow runs are invisible in the UI (Default collection not indexed, no job meta written) #238
Description
Environment: Ubuntu (kernel 7.0), RTX 5090 (Blackwell sm_120), NVIDIA driver w/ CUDA 13.3 userland, Modly AppImage v0.4.x, embedded Python 3.11.9, data dir relocated to a large secondary disk. Found while driving Modly headlessly (REST + MCP) for a game-asset pipeline.
Everything generated over the REST/MCP surface exists on disk but the app shows "No workspace assets are indexed yet" and empty Generate/Workflows views.
Three contributing causes:
POST /workflow-runs/from-imagehardcodes the"Default"collection (the legacy/generate/from-imageaccepts acollectionfield; the canonical endpoint does not).- The Workspace Library indexer only scans the
WorkflowsandExportsworkspace roots (ALLOWED_ROOTS), soDefault/output is never indexed. - API runs never write the
*.meta.jsonjob records that the collections view reads.
Workaround we use: mirror outputs into workspace/Exports/<set>/ and click "Refresh assets".
Suggested fix: accept collection on /workflow-runs/from-image, include Default in the indexer roots, and/or write job meta records from _run_generation.
Activity
fix(api): file /workflow-runs/from-image into the caller's collection (…
fix: close the follow-up gaps the second review pass found
Merge pull request #279 from kevin9327/fix/workflow-runs-collection
Lorchie commentedon Oct 9, 2026
Fixed in #279 (shipped in v0.4.2). POST /workflow-runs/from-image now accepts a collection field and files the output into that collection inside the workspace, so API-driven runs appear in the UI.
If API runs are still missing from the UI on v0.4.3, feel free to reopen this issue with the request you're sending.