Publishing changes not reflected on website.

Issues
#1

I’m experiencing a problem. When I publish my page, the process completes, and it indicates that everything is fine. However, the changes aren’t reflected on the live website. Everything was working properly until Friday.

This is the error:

Error: Error fetching loader data: Internal Server Error
    at r.fetchLoaderData (/vercel/path0/node_modules/@plasmicapp/loader-fetcher/dist/loader-fetcher.cjs.production.min.js:1:799)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async exports.PlasmicModulesFetcher.doFetch (/vercel/path0/node_modules/@plasmicapp/loader-fetcher/dist/loader-fetcher.cjs.production.min.js:1:2471)
    at async exports.PlasmicModulesFetcher.getCachedOrFetch (/vercel/path0/node_modules/@plasmicapp/loader-fetcher/dist/loader-fetcher.cjs.production.min.js:1:2397)
    at async exports.PlasmicModulesFetcher.fetchAllData (/vercel/path0/node_modules/@plasmicapp/loader-fetcher/dist/loader-fetcher.cjs.production.min.js:1:2101)
> Build error occurred
Error: Failed to collect page data for /[[...catchall]]
    at /vercel/path0/node_modules/next/dist/build/utils.js:991:15
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  type: 'Error'
}
Error: Command "npm run build" exited with 1
Deployment completed
BUILD_UTILS_SPAWN_1: Command "npm run build" exited with 1
#2

Are you still experiencing this error?

Can you share the Plasmic project url, and which page you are seeing issues with?

#3

I sent you the details. @yang

#4

@yang Wanted to follow up on this critical issue that is preventing us from deploying any changes at the moment. Thank you!

#5

Additional context: 41.3 build succeeds 41.4 build fails.