{"version":"2.1.223","anchor":"workflow-save-and-discovery-can-run-through-the-storage-back","canonical_anchor":"workflow-save-and-discovery-can-run-through-the-storage-back","heading":"Workflow save and discovery can run through the storage backend","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/workflow-save-and-discovery-can-run-through-the-storage-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Workflow save and discovery can run through the storage backend\n\nYour saved workflows can be listed and stored through a storage backend rather than plain files.\n\n**What**\n\nUser workflows can be enumerated and saved via storage keys instead of directory scans and file writes.\n\n**Details**\n\n- discovery pages through `listEntries`, counting near-miss extensions, oversize files and unreadable files\n- saving uses `mode: 384` and adds an `ifAbsent` precondition when not overwriting; an `AlreadyExists` result raises the existing name-collision error\n- cache invalidation and `tengu_workflow_saved` telemetry after a save were factored into a shared helper used by both the file and backend paths\n\n**Evidence**\n\n`could not be read through the storage backend`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}