Can't save or publish document

Prismic for Content Creators
1

image
image1870×649 103 KB

We found issue can't save or publish document open developer tools (F12) found CORS error how to fix this issue

2 Likes
2

Just to extend on this, we’re having the same issue but it’s affecting logging out on the dashboard and some changes are going through but several minutes later.

From a development perspective pushing model changes results in this error being thrown in the console:

Error: Invalid AWS ACL response from https://acl-provider.prismic.io/create
    at ScreenshotsManager.initS3ACL (<Repository Path>/node_modules/@slicemachine/manager/dist/managers/screenshots/ScreenshotsManager.cjs:79:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    ... 2 lines matching cause stack trace ...
    at async IncomingMessage.<anonymous> (<Repository Path>/node_modules/@slicemachine/manager/dist/_node_modules/r19/dist/createRPCMiddleware.cjs:17:45) {
  [cause]: DecodeError: Expecting string at 0.imgixEndpoint but instead got: undefined, Expecting { url: string, fields: { [K in string]: string } } at 0.values but instead got: undefined
      at _function.pipe.Either.foldW.value.value (<Repository Path>/node_modules/@slicemachine/manager/dist/lib/decode.cjs:20:14)
      at <Repository Path>/node_modules/@slicemachine/manager/dist/_node_modules/fp-ts/es6/Either.cjs:7:25
      at Module.pipe (<Repository Path>/node_modules/@slicemachine/manager/dist/_node_modules/fp-ts/es6/function.cjs:17:14)
      at Module.decode (<Repository Path>/node_modules/@slicemachine/manager/dist/lib/decode.cjs:18:20)
      at ScreenshotsManager.initS3ACL (<Repository Path>/node_modules/@slicemachine/manager/dist/managers/screenshots/ScreenshotsManager.cjs:64:45)
      at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
      at async PrismicRepositoryManager.pushChanges (<Repository Path>/node_modules/@slicemachine/manager/dist/managers/prismicRepository/PrismicRepositoryManager.cjs:196:7)
      at async Module.handleRPCRequest (<Repository Path>/node_modules/@slicemachine/manager/dist/_node_modules/r19/dist/handleRPCRequest.cjs:58:11)
      at async IncomingMessage.<anonymous> (<Repository Path>/node_modules/@slicemachine/manager/dist/_node_modules/r19/dist/createRPCMiddleware.cjs:17:45) {
    input: { message: 'Internal server error' },
    errors: [
      'Expecting string at 0.imgixEndpoint but instead got: undefined',
      'Expecting { url: string, fields: { [K in string]: string } } at 0.values but instead got: undefined'
    ]
  }
}
1 Like
3

Hey team,

Thanks for raising this - we can confirm we are currently experiencing an issue affecting the publication of new documents. The root cause has been identified as an ongoing incident with our cloud provider, which is impacting our services.

Our team is actively monitoring the situation and exploring possible mitigation options to minimize disruption while the provider works on a resolution.

You can follow along at https://status.prismic.io/, subscribe for updates there, and I'll also update this thread when we have news.

Apologies for the inconvenience, and thanks for your patience!

1 Like
4

Not able to save or publish documents

5

Hey @samia.honein, thanks for raising this - I've moved your post to this thread to keep information in one place. As was said above, we're currently experiencing an issue with our cloud provider and are working on minimising disruption.

6

An update for everyone: this is now fully resolved. If you see anything out of the ordinary, don't hesitate to let us know. Thanks for your patience!

7

Hi @Ezekiel, Save now working, but webhooks trigger update content not work, i try trigger test, but dont see log show update sucessful (i’m working with nextjs)

8

Hey @thanhnamnguyen, are you seeing any specific errors in the webhook tab of the settings?

9

Normally, when triggering or publishing, it shows the log when it succeeds or fails, but it doesn't show any information. And my website not update content because it not trigger.

I try another repo (hosted by Vercel - NextJS) it the same, not trigger by publish or manual click.

image
image2256×756 39.4 KB

10

Thanks for the details. What happens when you try to trigger this manually? Do you see any errors in the console? Can you switch the Status to "on" as well?

11

I try both, in status “on”, i update content and click publish → check log → no new log ‘api-update’ added → no new content in website.

In status ‘off’ i update content and click trigger test → check log

I dont see any errors, any logs.

12

Thanks for reporting this, we are still experiencing issues with webhook triggers, which may not fire or process events as expected.

The issue still originates from our cloud provider, and we continue to monitor their recovery while implementing mitigation measures on our side. I’ll keep this thread updated!

1 Like
13

All systems are now operational. Thanks for your patience everyone!

14

I am still unable to build my website. the build fails randomly when at one point “An invalid API response was returned“

15

This is the latest update from AWS:

[08:04 AM PDT] We continue to investigate the root cause for the network connectivity issues that are impacting AWS services such as DynamoDB, SQS, and Amazon Connect in the US-EAST-1 Region. We have identified that the issue originated from within the EC2 internal network. We continue to investigate and identify mitigations.

It seems they were improving earlier, but are back to experiencing problems with services affecting ours. You can follow along here for their updates: https://health.aws.amazon.com/health/status. I’m afraid until AWS completely declares their issues solved it might be in and out. We'll be updating our status page accordingly.