Urgent: Fail to update our schema in production

Feature(s) impacted

Failed to update our Forest Schema in our production environment

Observed behavior

After a successful code deployment we got an error message that there is a failure with updating schema in production

Also tried to publish new schema via forest-cli and got these messages:

after “forest deploy”
forest deploy
? Deploy layout changes to reference? Yes
× Source and destination environments must have the same schema. Please check your environments code is synchronized.

after “forest schema:apply”
Reading “.forestadmin-schema.json” from current directory…
Using the forest environment secret found in the environment variable “FOREST_ENV_SECRET”
Sending “.forestadmin-schema.json”…
× An error occured with the schema sent to Forest. Please contact support@forestadmin.com for further investigations.

Expected behavior

Schema will be updated successfully

Failure Logs

[31m “stack”: "Error: Internal Server Error\n at Request.callback (/usr/src/app/node_modules/forest-express/node_modules/superagent/lib/node/index.js:871:15)\n at /usr/src/app/node_modules/forest-express/node_modules/superagent/lib/node/index.js:1114:20\n at IncomingMessage. (/usr/src/app/node_modules/forest-express/node_modules/superagent/lib/node/parsers/json.js:22:7)\n at IncomingMessage.emit (events.js:412:35)\n at IncomingMessage.emit (domain.js:475:12)\n at endReadableNT (internal/streams/readable.js:1334:12)\n at processTicksAndRejections (internal/process/task_queues.js:82:21)"e[39m

e[31m[forest] :deciduous_tree::deciduous_tree::deciduous_tree: An error occured while computing the Forest schema. Your application schema cannot be synchronized with Forest. Your admin panel might not reflect your application models definition. Internal Server Errore[39m

Context

The issue happened when

  • Project name: Empathy
  • Team name: Engineering
  • Environment name: production
  • Agent type & version: forest-express 8.5.8
  • Recent changes made on your end if any: deleting smart segment

Hi @Avishai_Lippner :wave:

Sorry to read your message, we are currently looking at the issue.
It could be a replica of the incident we had last week. You can find more information on our status page here

Thanks for your patience.

@Avishai_Lippner

It should be good by now. Could you confirm that everything works as expected on your end ?

Thanks in advance :pray:

@jeffladiray
Thank you for your reply,
Unfortunately I can still see the deleted Smart Segment in our production environment

I’ve managed to update production schema with our development one using forest schema:apply (with production forest secret) and it seems to do the trick, so all good now
Thank you!

1 Like