Troubleshooting

• Check that Sudden is loaded on the pages where you play video.
• Make sure Sudden is initialized exactly once per page load.
• Confirm that there are enough concurrent viewers for the same content.
• Look at your browser console on a test page for any obvious initialization errors.

If everything looks healthy but savings remain low, sparse traffic is one possible reason.

• Temporarily disable Sudden and redeploy. If the issue remains, it is likely unrelated to Sudden.
• If disabling Sudden fixes the issue, check for:
  • JavaScript errors in the browser console.
  • Sudden being initialized more than once.
  • Any custom logic you added around Sudden that might interfere with your player.

• Compare browsers and devices: some older setups might not support Sudden and will quietly fall back to your CDN.
• Check whether affected users are on corporate networks, VPNs, or very restrictive environments.
• Confirm that the affected pages use the expected Sudden integration and client ID.

• Note the exact error message and on which page it appears.
• Confirm that you are using the recommended integration pattern from Getting started.
• Confirm that the clientId in your Sudden config is correct.
• Try on a clean browser profile or incognito window to rule out extensions.
• If your site enforces CSP, make sure all required Sudden sources are allowed. See the CSP requirements.

If you still see errors, gather:

• The page URL.
• A screenshot or copy of the error.
• Browser and device information.

and share them with your Sudden contact or support channel.