Step 1: Access the Solo Connect Dashboard
First, you need to know where to look. This central hub isn’t hidden.
To find the dashboard, navigate to:
Utilities > Admin tools > Solo Connect tab.
Here, you’ll see the main dashboard, which is split into two primary categories: Inbound Messages and Outbound Messages.
Step 2: How to Monitor Inbound Messages (Data Coming Into Solochain)
Inbound messages are all the pieces of data your WMS receives from other systems. Think new sales orders, purchase orders, or item updates from your ERP.
The dashboard shows you a quick summary of messages imported today, and most importantly, any errors.
How to Investigate and Fix Inbound Errors:
Let’s say you see a spike in errors. Don’t panic. Here’s the “how-to” for troubleshooting:
- Drill Down: Click directly on the error number to see a list of all failed messages.
- See the Problem: Select a message. On the right, you can see the exact content of the message that was received (e.g., the raw JSON file).
- Read the Error: At the bottom, a window tells you exactly what went wrong (e.g., “Item not found,” “Invalid data format”).
- Fix and Resend: Once you’ve made the fix (perhaps correcting the data in your ERP or a setup table in Solochain), you don’t need an external tool to resend the message. You can simply select the failed message and use the “Process” option to retry it.
- Pro-Tip for Testing: You can also use the “Import message” feature to simulate receiving data. Just paste your test message (like a JSON file) and select the correct importer type. This is perfect for testing new interfaces or fixes without involving the live ERP.
Step 3: How to Monitor Outbound Messages (Data Leaving Solochain)
Outbound messages are all the pieces of data Solochain sends to other systems. This includes things like shipping confirmations, inventory adjustments, and parcel costs.
This section also shows you messages sent today and any errors.
Understanding the “Waiting” Queue:
You might notice a “Waiting” category. This isn’t an error. It represents messages that Solochain has sent, but the other system hasn’t confirmed receiving them yet.
This is often used strategically. For example, instead of bombarding your ERP with thousands of individual parcel cost updates in real-time, you can bundle them up. Solochain will hold them in the “Waiting” queue and send them as one large batch at an off-peak time, like 3:00 AM, to avoid slowing down the ERP.
How to Handle Outbound Errors:
Just like with inbound messages, you have full power to troubleshoot.
- Drill Down: Click on the outbound error number.
- See the Context: You can view the content of the message Solochain tried to send and read the error details.
- Resend: After you’ve fixed the issue (maybe the ERP’s receiving endpoint was down), you have the same functionality to resend the message directly from this screen.
The consultants at LIDD work with organizations across the supply chain to build more efficient, sustainable, and resilient operations. If you’re looking to turn your business into a powerhouse of operational excellence, reach out to LIDD today.
