Start – Dashboard Error

Hi there,

Thanks for your message and for already trying the basic troubleshooting steps.

Could you please share the screenshot of the error you’re seeing and the exact steps to reproduce the issue?

Also, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:

• System Status Report which you can find via WooCommerce > Status
• Fatal error logs (if any) under WooCommerce > Status > Logs.

Please use https://pastebin.com/ or https://gist.github.com/ and share a link to that paste in reply here. Once we have more information, we’ll be able to assist you further.

Hi @merome,

Thanks for sharing the System Status Report and the screenshot, I appreciate the details you included.

The Pastebin link you shared appears to be password protected, so I am unable to view it. Please re-share the SSR using an unlisted paste without a password, or use https://gist.github.com/ and share the viewable link.

The screenshot did not display for us, please upload it using https://snipboard.io and share the link here, and we will continue from there.

Hi @merome, thanks for sharing the SSR and the screenshot, that really helps, the inbox on the WooCommerce Home screen is powered by a REST request plus scheduled actions, and the message you are seeing usually means that request is failing before the data can be returned

From the SSR I can see Action Scheduler reports 237 failed actions, so the first thing I want to check is whether one of those failures is coming from WooCommerce Admin, please go to WooCommerce > Status > Scheduled Actions, filter by Failed, and tell me which hooks are failing, a screenshot is perfect if that is quicker

While you are there, also open WooCommerce > Status > Logs, select the latest fatal-errors log, and share the last entries, that will show whether something is causing a 500 error behind the scenes

One quick sanity check you can do in the meantime is open https://shop.pgoe.at/wp-json/ in your browser and confirm it loads, if it does not, that would confirm a REST API issue, in which case temporarily disabling caching or security plugins like WP Fastest Cache for a minute can help narrow it down

Hi there!

Thank you for sharing the screenshot. The screenshot does not contain much information.

To assist you further, could you please create a staging site, deactivate all plugins except WooCommerce, activate a default theme like Twenty Twenty-Five, and try to replicate the issue again?

Here is the complete guide on how to run a conflict test:
https://woocommerce.com/document/how-to-test-for-conflicts/

You can use the following plugin to create a staging site:
https://ww.wp.xz.cn/plugins/wp-staging/

Let us know if you still face the same issue.

Hi @merome,

Thanks for the update, I appreciate you sharing that detail.

Since this is a multisite setup, could you let us know if the issue with the WooCommerce Start/Dashboard (Inbox not loading) is affecting all sites on the network, or just this one site?

Also, many hosting providers offer a built-in staging feature. Could you check if your host provides this? If yes, you could create a staging copy of the entire multisite and run the conflict test there safely, which would help narrow down the cause without affecting your live environment.

Let us know what you find 👍

Hi @merome,

No, you definitely don’t need to activate WooCommerce on any of the non-shop subsites. The conflict test can be done directly on the WooCommerce subsite itself.

While you’re doing that, going back to the 238 failed actions, could you also share a few more screenshots of those failed hooks? The first three you shared were helpful but we’d like to see more to identify if there’s a pattern, particularly any hooks related to woocommerce_admin or remote notifications, as those are often tied to the inbox failing to load.

Looking forward to your findings!

Hi there!

Thank you for the update.

Shiptastic: shipments_tracking and daily_cleanup are not part of core WooCommerce. These are created by third-party plugins, so they should not directly cause the issue you are facing.

Could you please run a conflict test and see if that works for you?

Let us know what you find.

Hi there!

Thank you for the update.

Could you please confirm if you cleared your browser cache and site cache after deactivating all plugins?

Also, just to verify did you deactivate all plugins, or were some plugins left active?

To help us investigate further, could you please enable debug logging on your site and share the logs with us? This will allow us to check if there are any underlying errors causing this behavior.

You can enable debug logging by following these steps:

1. Access your site files (via FTP or your hosting file manager).
2. Open the wp-config.php file located in the root directory.
3. Look for the line: define( ‘WP_DEBUG’, false );
4. Replace it (or add the following lines if not present):

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

5. Save the file.

After that:

• Reproduce the issue on your site.
• Then go to: wp-content/debug.log
• Copy the contents of that file and share it with us (you can paste it here or upload it to a service like Pastebin).

Once we have the log, we’ll be able to take a closer look and guide you further.

Thank you for cooperation and understanding