Advanced Reporting troubleshooter for Adobe Commerce
This article provides a structured troubleshooting decision tree for diagnosing and resolving Advanced Reporting issues in Adobe Commerce. It guides you through targeted diagnostic questions and directs you to the relevant queries, patches, or documentation based on your answers. The workflow helps identify root causes such as configuration gaps, currency mismatches, token issues, and cron‑related failures.
Description description
Environment
- Adobe Commerce on Cloud Infrastructure
- Adobe Commerce on-premises
Issue/Symptoms
- Advanced Reporting dashboard doesn’t display any data
- 404 error when accessing Advanced Reporting
- Synchronization delays between Adobe Commerce and Advanced Reporting
- No callbacks found for cron job analytics_collect_data
- Missing or invalid token in configuration
- Multiple base currencies detected in configuration or historical orders
- Cron job analytics_collect_data missing, failed, or stuck in error state
Resolution resolution
Click on each question to reveal the answer details in each step of the troubleshooter.
Step 1
- YES – Proceed to Step 2.
- NO – Complete the Advanced Reporting requirements for your site by following the steps in Advanced Reporting requirements. Then, proceed to Step 2.
Step 2
NOTE: This command requires a full table scan, so for tables with high numbers of records, this could have a performance impact whilst the query is executing to obtain historical orders data.
- YES – If multiple rows are returned by
SELECT value FROM core_config_data WHERE path = 'currency/options/base';, Advanced Reporting is not supported. We only support one currency. You will have to use Adobe Commerce Intelligence instead. Reach out to your Account team to set this up. - NO – If only one currency (e.g., USD) is shown, check historical orders with
SELECT DISTINCT base_currency_code FROM sales_order;. If multiple currencies ever existed, Advanced Reporting is not supported. Otherwise, proceed to Step 3.
Step 3
> Stores > Settings > Configuration > General > Advanced Reporting. For detailed steps, review Advanced Reporting: Enable Advanced Reporting.- YES – Proceed to Step 4.
- NO – Enable Advanced Reporting in Admin
>Stores>Settings>Configuration>General>Advanced Reporting. Wait 24 hours for sync. If data loads, issue resolved; if not, proceed to Step 4.
Step 4
SELECT * FROM core_config_data WHERE path LIKE 'analytics/general/token' \G to check.- YES – Proceed to Step 6.
- NO – If token is NULL or missing, proceed to Step 5.
Step 5
flag table?- YES – Delete the row by running
DELETE FROM flag WHERE flag_code = 'analytics_link_subscription_update_reverse_counter';, disable/enable Advanced Reporting, reauthorize token, wait 24 hours. If still broken, submit a support ticket. - NO – Disable/enable Advanced Reporting, reauthorize token, wait 24 hours. If still broken, submit a support ticket.
Step 6
core_config_data contain both a crontab/default/... and a crontab/analytics/... row for analytics_collect_data? A cron_schedule row alone does not confirm that the job is registered under the correct cron group.Run this query:
| code language-none |
|---|
|
-
YES (both rows) – Verify that the analytics-group row is present and identify the obsolete default-group row. Following your normal backup and change-control process, remove only the confirmed legacy row:
code language-none DELETE FROM core_config_data WHERE config_id = <verified_legacy_config_id> AND scope = 'default' AND scope_id = 0 AND path = 'crontab/default/jobs/analytics_collect_data/schedule/cron_expr';After removing the row, clear the configuration cache: on Adobe Commerce on Cloud Infrastructure, use the supported deployment/cache process; on-premises, run
bin/magento cache:clean config. Verify thatanalytics_collect_dataruns successfully on its next scheduled execution, then allow 24–48 hours for Advanced Reporting to refresh. Proceed to Step 7. -
NO (only the analytics row, only the default row, or no rows) – If only the
crontab/analytics/...row exists, no legacy row needs removing. Proceed to Step 7. Otherwise, disable and re-enable Advanced Reporting, then re-run the query. If both rows now exist, follow the YES steps above. If only the analytics row now exists, proceed to Step 7. Do not delete the only existing row and do not insert rows manually. If the analytics-group row is still missing, do not continue. Check the installed Adobe Commerce version, the cron group setup, and any applicable patch or configuration guidance, or submit a support ticket.
Step 7
cron_schedule table, and was the analytics_collect_data job executed (check using SELECT * FROM cron_schedule WHERE job_code LIKE 'analytics_collect_data' \G)?-
YES – If status = missed this indicates that the
analytics_collect_datawas not executed as expected. This issue can still occur in supported Adobe Commerce versions because the job originally ran in the default cron group. Apply the QPT patch MDVA-19640. Before applying, upgrade to the latest version of the Quality Patches Tool (QPT). Follow patch application instructions in the official QPT usage guide:- QPT usage guide
- QPT release notes: v1.0.20 (MDVA-19640 added in v1.0.20).
-
YES – If status = success, proceed to Step 9.
-
YES – If status = error, the job attempted to run but encountered an error. Proceed to Step 8 for further diagnostics.
-
NO – No records found. The job never ran. Proceed to Step 8.
Step 8
analytics_collect_data job logged in support_report.log?For Adobe Commerce on Cloud, use New Relic Logs as the preferred method to check this because logs can be generated on multiple web nodes and are not synchronized into a single local file on the server. New Relic aggregates per-node and rotated logs in one place.
In New Relic, go to Logs and run the query:
| code language-none |
|---|
|
As an alternative/manual check, run zgrep analytics_collect_data var/log/support_report.log*.
- YES – If the job is logged successfully, proceed to Step 9.
- NO – Submit a support ticket.
Step 9
data.tgz file exist and are there records in access logs?Run the following command to check for the data.tgz file:
| code language-none |
|---|
|
For the access logs, for Adobe Commerce on Cloud, use New Relic Logs as the preferred method to check this because logs can be generated on multiple web nodes and are not synchronized into a single local file on the server. New Relic aggregates per-node and rotated logs in one place.
In New Relic, go to Logs and run the query:
| code language-none |
|---|
|
For on-prem, use an alternative/manual check like:
| code language-none |
|---|
|
- YES – If the file
data.tgzis present and there are records in the access logs, but you still have a 404 error, you need to submit a support ticket. - NO – Proceed to Step 10.
Step 10
Example: In the cron_schedule table you see the error The “/app/var/tmp/analytics/tmp/.nfsb3b6041dd44588a0000850c0 file can’t be deleted. Warning! unlink(/app/var/tmp/analytics/tmp/.nfsb3b6041dd44588a0000850?lang=en): No such file or directory”
- YES – This issue is automatically resolved on Adobe Commerce on Cloud through the Cloud patches included with ECE Tools. No manual action is required. For on‑premises merchants, this fix is not available through the Quality Patches Tool (QPT). If the error persists, please submit a support ticket.
- NO – Submit a support ticket.
Related reading
Advanced Reporting in the Commerce Admin Getting Started Guide.