Yodeck — Troubleshooting

📘
Related setup guide
Setting up Yodeck? See the Yodeck connector setup guide.

Error message	Likely meaning (TL;DR)	Recommended next steps
Yodeck rejected the API token (Invalid or empty authentication token). Check that Token Name and API Token come from the same Yodeck token.	Most often the token name contains a space: Yodeck sends the name inside the authorization header and rejects any name with a space. Otherwise the name and value don't belong to the same token, or the token was deleted in Yodeck.	In Yodeck open Account Settings → Advanced Settings → API Tokens. If the token name has a space, generate a new token with a name that has none (for example `xyte-connector`), then re-authorize the connector with the new name and value. If the name has no space, generate a new token anyway and enter both values again.
Yodeck returned 403 — this API token's role cannot read screens. The token needs at least the Content & Device Manager role; Content Viewer is not enough.	The token's role is too low (for example Content Viewer), or it has no role on the workspace that holds the screens.	Generate a token with the Content & Device Manager role (or higher) on every workspace whose screens you want in Xyte, then re-authorize the connector.
Yodeck is currently rate-limiting requests. Please try again later.	Yodeck is temporarily throttling API calls.	Wait a few minutes and try again. During regular syncs Xyte retries automatically.
Unable to authenticate against Yodeck.	Xyte couldn't validate the credentials against Yodeck for a reason other than the ones above.	Confirm the Yodeck plan includes API access (Premium or Enterprise), check both values and try again. If it keeps failing, contact Xyte support.
A screen shows as Unavailable	The screen exists in Yodeck but isn't registered to a player yet.	Register (pair) the screen in Yodeck. It reports status on the next sync.
Connector is Active but Devices found is 0	The Yodeck account has no registered screens, or the token's workspace role doesn't cover the workspace that holds them.	Register a screen in Yodeck, or add a role for the right workspace to the token. The count updates on the next sync (every few minutes).
Only some of the screens appear in Xyte	The missing screens are in a workspace or sub-workspace the API token has no role in. A role on a parent workspace doesn't include its sub-workspaces, so screens in those sub-workspaces are invisible to the token.	In Yodeck open Account Settings → Advanced Settings → API Tokens and edit the token you gave Xyte. Either turn on Global Admin (recommended: it covers every workspace and sub-workspace, including new ones), or click Add New Role and give the token the Content & Device Manager role on every sub-workspace that has screens. You keep the same token, so nothing changes in Xyte; the missing screens appear on the next sync, usually within a few minutes.