Embedded documents do not render and appear all black

​@trevor what you’re describing is typically caused by a validation issue after the initial load, most often related to the embed token or origin.

A few things to double-check:

• The origin used when generating the token must match the domain hosting the iframe exactly, including protocol (https://) and any subdomains. Even small differences can cause the embed to fail after loading.

• Make sure the token is being used shortly after it’s generated and hasn’t expired.

• The embedId, origin, and token all need to align correctly—any mismatch can invalidate the session.

• If you haven’t already, check the dev console for any CSP or iframe-related errors that might show why rendering is being blocked.

If everything looks correct, it would be helpful to confirm the following:

• The exact origin string being sent in the token request

• The full iframe URL being used

• Any console errors that appear when the screen goes black

That should help narrow down whether this is an origin validation issue or something else.

Hello ​@trevor , thank you for posting your question.

We are doing some research on our end to determine what scenarios could cause this issue. It appears to be some sort of bootstrapping failure where the initial rendering of the canvas is succeeding, but then something fails causing the canvas to go black.

We have heard reports of this behavior before, but have been unable to identify a cause before it either went away “magically” or we were unable to get ahold of the reporter to follow up. Its our expectation that something changed such that they no longer had the issue. But, we do not know if that change was caused by us or them.

I will be in touch soon with additional questions. In the meantime, can you send the exact parameters of the iframe which is containing this embed? Perhaps there is a parameter we aren’t handling correctly.