{"version":"2.1.248","anchor":"the-sync-action-is-wired-up-but-compiled-out-of-this-build","canonical_anchor":"the-sync-action-is-wired-up-but-compiled-out-of-this-build","heading":"The sync action is wired up but compiled out of this build","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/the-sync-action-is-wired-up-but-compiled-out-of-this-build","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### The `sync` action is wired up but compiled out of this build\n\nThe artifact sync action is routed everywhere but compiled out of this build.\n\n**What**\n\nAlthough permission checks, result rendering and the action list all route `sync` through, the two modules that implement it are compiled to nothing in this build, so the action is never offered and cannot be used. There is no flag to turn it on; it is a build-time exclusion, and asking for it returns \"sync is not available in this build\".\n\n**Details**\n\n- Both module handles are constants set to null, and a neighbouring stub reports that artifact rooms are not compiled into this build.\n- Because those handles are null, the live-edit gate check that would advertise `sync` is never reached.\n- None of this handling exists in the previous release, so the action is entirely new.\n\n**Evidence**\n\n`sync is not available in this build`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}