Have you set up the slice-simulator page in your project? It seems like it might be treating it as a normal Prismic page and expecting to retrieve content via your /page/[...uid] route.
Hi @samlittlefair I'm running into this issue where the netlify hosted website is behind password protection while the client enters content before launch (some clients are like this and want passwords while the website is being worked on.).
This obviously means that the prismic backend cannot reach slicemachine, so the slice previews show 'error'
Is there anyway around this? Maybe a password config for slicemachine to be able to reach netlify?