a year ago
(no markdown available for this content)
11 Replies
a year ago
project id: 004e54e7-64a6-467d-960d-379e6d29e925
env: 863733ef-0852-4eae-8969-095ca2bf49f1
trying to sync env from staging: 3b4a2665-b591-4f42-9172-5e7bc381ecdd
a year ago
Hey, is this still an issue, we recently pushed a change to fix something that would cause that error
a year ago
i'll see if it still happens during the week, sometimes it broke sometimes not
a year ago
sounds good!
a year ago
i'm still getting the same error
a year ago
can you get the api reponse from that call?
a year ago
{
"errors": [
{
"message": "Invalid patch",
"locations": [
{
"line": 2,
"column": 3
}
],
"path": [
"environmentStageChanges"
],
"extensions": {
"code": "INTERNAL_SERVER_ERROR"
},
"traceId": "5533840160134990015"
}
],
"data": null
}a year ago
could you please also share the API request
a year ago
there's sensitive data there, can you use my environment to reproduce it?
go to sync, select the staging environment and wait until invalid patch is shown (do not apply the changes)
a year ago
got it, perfect ty
a year ago
fix incoming