Server-side module corruption killed our project overnight. Live commercial site frozen. Support's answer: copy from a duplicate that doesn't exist

Our production site (fftech.ai) is built on Framer. During the night of 19-20 August, with nobody in the project and zero document changes, every local component stopped resolving. The canvas shows:

Error in local-module:layoutTemplate/f3ZoosNUp:default - Component does not exist.

The console shows:

[CodeGenerationStore] ServiceError.UnknownError: unrequested module "LuvZpQNReCkILJAhZidM" and save "au4quZTQSz6As56GLNAs"

plus a 400 from the module lookup endpoint.

Before anyone suggests the standard steps - we have done all of them, and the results matter:

Version history shows no saves in the breakage window. The document did not change; the backend did. Restoring known-good versions from before the breakage fails with the identical error, which should be impossible if the document were the problem. Fresh duplicates inherit the failure. Quick Actions cannot locate the referenced module. Two team members on separate machines reproduce it on any fresh load - a session that stayed open kept working until restart, so the failure arrives with a fresh fetch of project state. Shared workspace component folders resolve fine; only this project's local module store is dead.

Every fact points the same way: the server-side module store for this project is corrupted. No user action caused it, and no action available in the editor can fix it.

The consequence: a live commercial site we can neither edit nor safely publish, since publishing from this state would replace the working production bundle with a broken one. We are rebuilding the entire site from scratch tonight to regain control of our own website.

1/2

Server-side module corruption killed our project overnight. Live commercial site frozen. Support's answer: copy from a duplicate that doesn't exist

Our production site (fftech.ai) is built on Framer. During the night of 19-20 August, with nobody in the project and zero document changes, every local component stopped resolving. The canvas shows:

Error in local-module:layoutTemplate/f3ZoosNUp:default - Component does not exist.

The console shows:

[CodeGenerationStore] ServiceError.UnknownError: unrequested module "LuvZpQNReCkILJAhZidM" and save "au4quZTQSz6As56GLNAs"

plus a 400 from the module lookup endpoint.

Before anyone suggests the standard steps - we have done all of them, and the results matter:

Version history shows no saves in the breakage window. The document did not change; the backend did. Restoring known-good versions from before the breakage fails with the identical error, which should be impossible if the document were the problem. Fresh duplicates inherit the failure. Quick Actions cannot locate the referenced module. Two team members on separate machines reproduce it on any fresh load - a session that stayed open kept working until restart, so the failure arrives with a fresh fetch of project state. Shared workspace component folders resolve fine; only this project's local module store is dead.

Every fact points the same way: the server-side module store for this project is corrupted. No user action caused it, and no action available in the editor can fix it.

The consequence: a live commercial site we can neither edit nor safely publish, since publishing from this state would replace the working production bundle with a broken one. We are rebuilding the entire site from scratch tonight to regain control of our own website.

1/2