fullmetrixDocs

Troubleshooting

Fix Magento module problems, from a missing menu to connection errors and data that stops moving.

Always start with checks that change nothing. Do not click Disconnect, either in Magento or in Fullmetrix, to "start over". In Magento, disconnecting erases the link with Fullmetrix and the code cannot be reused. In Fullmetrix, it deletes the imported data.

Several checks on this page run on the command line. Pass them on to your developer.

The two diagnostic commands

From the Magento project folder, your developer runs these two commands.

bin/magento module:status Fullmetrix_Connector
bin/magento fullmetrix:status

The first one confirms the module is enabled. The second one shows the connection status, line by line.

LineWhat it shows
VersionThe installed module version
Registeredyes if the store is connected to Fullmetrix, no otherwise
Connection codeThe code in use. Hide this line before sharing the output.
Webhooksenabled if changes are being sent
QueueThe number of changes waiting to be sent and the age of the oldest one
orders, customers, products...The number of items the store can send, per type

A Queue that stays at or near 0 is normal. A queue that grows hour after hour means the cron is not running or sending to Fullmetrix is blocked.

The Fullmetrix menu does not appear in Magento

  1. Sign out of the Magento admin and sign back in. The menu is often cached in the session.
  2. Your developer checks that the module is enabled with bin/magento module:status Fullmetrix_Connector. If it is not, they run bin/magento module:enable Fullmetrix_Connector.
  3. They run bin/magento setup:upgrade, then bin/magento setup:di:compile if the store is in production mode, then bin/magento cache:flush.
  4. If you use a custom admin role, check that the Fullmetrix resource is ticked, as explained in Compatibility.

Connection error messages

When the connection fails, Magento shows Échec de la connexion (connection failed) followed by a reason. On the command line, the reason follows the message Connexion echouee. Some reasons come back in French even in an English admin. They are quoted below as they appear.

Reason shownWhat it meansWhat to do
invalid_code_formatThe code does not have the form FMTX-XXXX-XXXX-XXXXCopy it again from Fullmetrix. It never contains the letters O and I or the digits 0 and 1.
invalid_storeThe chosen store view does not exist or is not activeChoose an active view. On the command line, check the number passed to --store-id.
Code de connexion introuvableThis code does not exist in FullmetrixCopy the code shown in your organization again, with no extra characters
Plateforme incorrecte pour ce codeThe code was created for another platformIn Fullmetrix, go back to the platform choice, choose Magento, then copy the code shown and try again
Ce code est déjà associé à un autre siteA store has already accepted this codeSee the next section
Trop de tentatives, réessayez dans quelques minutes.Too many attempts in a short timeWait ten minutes before trying again
Cette boutique est déjà connectée à une autre Organization.The store already belongs to another Fullmetrix organizationUse that organization, or remove the store from it first
Cette boutique a déjà bénéficié d'un essai Fullmetrix...The free trial was already used for this storeA subscription is required, see Billing
invalid_response, HTTP followed by a number, or a network messageThe server could not reach Fullmetrix properlyYour developer checks that the server can open outgoing HTTPS connections to fullmetrix.com (firewall, proxy, DNS, certificates)

The code is "already associated with another site"

A code works only once. This message, Ce code est déjà associé à un autre site, appears when you retry with a code that was already accepted, for example after clicking Disconnect in Magento, or if another installation (a staging site, for example) used it first.

If the store card in Fullmetrix still works, there is nothing to do, the connection is in place. If you disconnected the store in Magento and want to reconnect it, you need a new code. Open Settings, then Integrations, click Disconnect on the Magento card, confirm, then add the store again to get a fresh code. This erases the data imported into Fullmetrix, which is then imported again from your store.

The store is connected but data stops moving

  1. In Magento, open Marketing, then Fullmetrix, and check that the Connected badge is still shown.

  2. Your developer runs bin/magento fullmetrix:status and looks at the Queue line. If it grows, the cron is not running or sending is blocked.

  3. They check that the Magento cron is installed and running, then run the Fullmetrix group once to test.

    bin/magento cron:run --group=fullmetrix
  4. They look at var/log/system.log and var/log/exception.log around the time of the problem.

  5. In Fullmetrix, open Settings, then Integrations, and read the Magento card. A red message gives the cause of the last error.

The Fullmetrix card says the store is unreachable

The message The last sync could not reach your store. Make sure it is online and publicly reachable. No data was updated. means Fullmetrix could not call your site. Check that the store is online, not in maintenance mode, and that no protection blocks the /fullmetrix/api/ addresses. If you use Cloudflare, follow Cloudflare and firewalls.

After an error, the Sync button gives way to Resume and Reset. Once the cause is fixed, click Resume to continue from where the import stopped. If Resume isn't offered, click Reset, which sets the progress back to zero and restarts the sync without deleting orders already imported. This also applies when the card shows Auto-sync disabled after N consecutive errors, even though that message mentions the Sync button. The card's other states are described in Sync status.

Errors appear after a module update

On a store in production mode, every module update must be followed by bin/magento setup:upgrade, bin/magento setup:di:compile and bin/magento cache:flush. If one of these commands was forgotten, errors can appear in the admin or at checkout. Your developer runs the three commands again, in this order.

Visitor tracking receives nothing

  • Check that the store is connected, with the Connected badge in Magento.
  • Clear Magento's page cache or your external cache, so the pages served include tracking.
  • Run your test after accepting cookies if a consent banner is in place.
  • Check delivery in Tracking script.

Contact support

If the problem persists, contact us with the following.

  • The Magento or Adobe Commerce version and the PHP version.
  • The output of bin/magento fullmetrix:status, with the Connection code line removed.
  • The connected store view and the store's public address.
  • The exact message and the time it appeared.
  • Whether there is a firewall, Cloudflare, maintenance mode or a password on the site.
  • Relevant lines from the Magento logs, with no customer data.

Never send a password or the connection code.

On this page