Title: Disabling Heartbeat Triggers Javascript Error Last modified: September 8, 2022 --- # Disabling Heartbeat Triggers Javascript Error * Resolved [generosus](https://wordpress.org/support/users/generosus/) * (@generosus) * [3 years, 9 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/) * Good Day, * When we disable Heartbeat in the backend, your plugin reports a JavaScript error. * The JavaScript error is: [Missing Dependencies: wp-auth-check](https://prnt.sc/ydQRFRFkncta) * At first, we thought the error was caused by our caching plugin [SG Optimizer](https://wordpress.org/plugins/sg-cachepress/). As it turns out, however, it appears the error is simply a Query Monitor alert suggesting the affected website’s Heartbeat is disabled. * For more useful information, please refer to the following: * [SGO Heartbeat Trigerring Javascript Error](https://wordpress.org/support/topic/sgo-heartbeat-triggering-query-monitor-error/) * [Missing Dependencies upon heartbeat deactivation](https://wordpress.org/support/topic/missing-dependencies-upon-heartbeat-deactivatton/) * [Disabling Heartbeat causes Missing Dependencies error in Query Monitor](https://github.com/wp-media/wp-rocket/issues/4032) * So, based on the above, shouldn’t your plugin code be adjusted to reflect a more accurate error message — or — disregard the Heartbeat condition by not displaying the error message at all? It’s creating confusion and causing many to chase what appears to be a “false positive.” * Until then, we’ll simply follow [SiteGround’s advice on this matter](https://wordpress.org/support/topic/sgo-heartbeat-triggering-query-monitor-error/#post-15990543). * Thank you. Viewing 9 replies - 1 through 9 (of 9 total) * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [3 years, 9 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/#post-15991991) * Unfortunately there is a lot of misinformation about this out there in blog posts. If you deregister a script or stylesheet but don’t dequeue it then that’s an error and the message that QM displays is correct because this is a broken dependency. * If you deregister and/or dequeue a script or stylesheet but something else depends on it, that’s also an error, and the message that QM displays is this case is also correct because this is a missing dependency. * My comment here pretty much says the same thing: [https://wordpress.org/support/topic/suppress-presistent-errors-ex-broken-dependencies-wp-auth-check-on-wp-engine/#post-8219868](https://wordpress.org/support/topic/suppress-presistent-errors-ex-broken-dependencies-wp-auth-check-on-wp-engine/#post-8219868) * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [3 years, 9 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/#post-15992002) * By the way this isn’t a “false positive”, it’s an actual error, albeit a relatively common one due to several hosting providers who disable heartbeat in this manner. * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [3 years, 9 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/#post-15992016) * To clarify further about the effect: The `wp-auth-check` script is probably broken on your site because it depends on heartbeat which does not exist. It’s the reason QM reports it as a broken dependency. * Thread Starter [generosus](https://wordpress.org/support/users/generosus/) * (@generosus) * [3 years, 9 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/#post-15992093) * (EDITED) * Hi [@johnbillion](https://wordpress.org/support/users/johnbillion/), * So, for the ignoramus … * Other than Heartbeat being disabled, what else may cause `wp-auth-check` to break? We haven’t modified any WP files. * Also, from previous reports and acknowledgements, it appears that some caching plugins could be the culprit. * Thank you. * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [3 years, 9 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/#post-15992150) * `wp-auth-check` is a script that depends on `heartbeat` in order to function ( it’s the script that ultimately shows a popup login window if your user session expires while you’re in the middle of doing something). Because `heartbeat` is missing, `wp-auth-check` won’t work. * Thread Starter [generosus](https://wordpress.org/support/users/generosus/) * (@generosus) * [3 years, 9 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/#post-15992167) * That helps a lot! We’ll perform additional backend checks to see if anything else (other than caching plugins) could be causing this issue with our website. * Cheers! * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [3 years, 9 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/#post-15992215) * I suspect it’s just the disable heartbeat option in the SGO plugin. If you switch that off, heartbeat’s heart will start beating again, and wp-auth-check will be happy. * [filmdc](https://wordpress.org/support/users/filmdc/) * (@filmdc) * [3 years, 7 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/#post-16183695) * [@johnbillion](https://wordpress.org/support/users/johnbillion/) Thank you for taking the time to explain this clearly for us less knowledgeable. Are these heartbeats disabled in response to the zero-day that was in the news years ago? * Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * (@johnbillion) * WordPress Core Developer * [3 years, 7 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/#post-16184571) * I don’t believe so, no. Some hosting companies disable it to reduce the load on the server. Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘Disabling Heartbeat Triggers Javascript Error’ is closed to new replies. * ![](https://ps.w.org/query-monitor/assets/icon.svg?rev=2994095) * [Query Monitor](https://wordpress.org/plugins/query-monitor/) * [Frequently Asked Questions](https://wordpress.org/plugins/query-monitor/#faq) * [Support Threads](https://wordpress.org/support/plugin/query-monitor/) * [Active Topics](https://wordpress.org/support/plugin/query-monitor/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/query-monitor/unresolved/) * [Reviews](https://wordpress.org/support/plugin/query-monitor/reviews/) ## Tags * [heartbeat](https://wordpress.org/support/topic-tag/heartbeat/) * [Missing Dependencies](https://wordpress.org/support/topic-tag/missing-dependencies/) * 9 replies * 3 participants * Last reply from: [John Blackbourn](https://wordpress.org/support/users/johnbillion/) * Last activity: [3 years, 7 months ago](https://wordpress.org/support/topic/disabling-heartbeat-triggers-javascript-error/#post-16184571) * Status: resolved