Check and Troubleshoot Your Magento Connection
2 min read
When a Magento action in chat does not work, work through these checks from the quickest to the most detailed.
1. Test Connection
In Velaro, open Integrations, then Magento, and click Test Connection. You should see your store name and version. If not, the token or store URL needs attention.
2. Read The Activity Log
The Magento Activity Log tab records every request Velaro made to your store and what came back, including errors. This is the fastest way to see whether a failure came from Magento or from somewhere else.
3. Use The Diagnostic Tools
If you use the Velaro MCP connection or the Velaro command line, these tools are available for your site:
| Tool | What it does |
|---|---|
| magento_diagnose | Checks the connection, access and skills in order and stops at the first real problem |
| magento_test_connection | Same check as the Test Connection button |
| magento_list_stores | Lists the store views Velaro can see |
| magento_activity_logs | Reads the Activity Log |
| magento_search_products, magento_search_orders, magento_get_order, magento_search_customers | Run a real lookup against your store to confirm data comes back |
4. Meaning Of Common Errors
| Result | Meaning and fix |
|---|---|
| 401 | The token was revoked or the integration is not activated in Magento. Activate it and paste the new token. |
| 403 naming a resource | The integration lacks that access, for example Sales, Customers, Carts or Marketing. Edit the integration in Magento and grant it. |
| Empty results where data exists | Check access and that the products or orders are in the store view Velaro is connected to. |
| B2B actions say Adobe Commerce is required | Company accounts, requisition lists and negotiable quotes exist only on Adobe Commerce. |
Testing Every Magento Skill
Velaro runs a standard test of all the Magento skills against a test store after changes: read actions run as is, write actions run only with safe throwaway values (a one percent single use coupon, a cart, a comment on a designated test order), and refund and cancel actions run only in a dry form against an order number that does not exist, where the correct result is a clear not found message. A failure also has to appear in the Activity Log, or it counts as a failure of its own. Run your own version on a test store, never on live customer orders.
If you would like Velaro to run this test for your store, contact your Velaro account team.
Email
Was this article helpful?
Shopify Integration — Full Guide