Hitting 500 error from the codegen endpoint

Issues
1

Hitting 500 error from the codegen endpoint

image.png
image.png1478×880 176 KB

2

Thanks for the report! I think it should work now, but we’re looking into it

3

Still hitting it unfortunately

4

same

> Build error occurred
FetchError: invalid json response body at <https://codegen.plasmic.app/api/v1/loader/code/versioned?cb=5&platform=nextjs&loaderVersion=2&projectId=...TR%401.0.0> reason: Unexpected token < in JSON at position 0
    at ..node_modules/node-fetch/lib/index.js:272:32
    at processTicksAndRejections (internal/process/task_queues.js:95:5) {
  type: 'invalid-json'
}
5

Could you send me the project IDs? Thanks!

6

sent in DM

7

We are deploying a fix

8

Should now be resolved; sorry about that :pensive:

9

out of curiosity, what’s the short-form post-mortem?

10

We updated our data model schema. Usually there is a background migration that happens that incrementally performs the schema upgrade, though due to a configuration error that failed to run. We also perform live migration for data requests that happen before background migration is finished; the live migration was causing the 500 because some of the forked processes of our express server were not able to find the proper database configuration.

11

We’ve added some new live monitoring to catch issues like the above

12

:thumbsup: thank you!

13

working for us again!

14

thanks