Troubleshoot policies

Review the points in this table if Script Management isn't behaving as expected.


The dashboard is empty

If there's no real-user monitoring (RUM) beacon data available, the View and Edit Configuration table on the Script Management dashboard will be empty. Check that:

If after all of this, the table is still empty, talk to ‚ÄčAkamai‚Äč customer support.

Dashboard data is missing

This could be because certain scripts generated enough RUM beacons for Script Management to detect them, and you've set up your policy to defer or block them. As a result, there aren't enough beacons to provide data. Basically, your policy is doing its job.

Scripts are not deferred or blocked

If the policy isn't applied or the service worker isn't functioning, scripts that the policy should defer or block might be allowed to run on your site.

After performing these checks, allow a few minutes for the policy to propagate and reload the page in the browser. If this doesn't resolve the issue, talk to ‚ÄčAkamai‚Äč customer support.

A script set to No Action is blocked

If functionality on your site stops working, although the script that runs it is set to No Action in the policy, it might be because one JavaScript is referencing another. The script that you want to run might be dependent on a script that you blocked or deferred.

Slow network simulation stops working

If some functionality on your site stops working when you're simulating a slow-network connection, Script Management's Single-Point-of-Failure Protection feature might be intervening with scripts because of the network conditions.

Check the timeout range limits, located in the Advanced settings:

  1. Disable Single-Point-of-Failure Protection and monitor site performance.

  2. If that resolves the issue, try increasing the lower limit you've set for the Timeout range limits, and re-enable Single Point of Failure Protection.