When something goes wrong in your integration, Junipeer gives you two tools to diagnose what happened, and a clear path to get help when you need it. This guide walks through both.
Use the Entities view to spot issues
The Entities view in the Junipeer app gives you a real-time overview of every order, invoice, product, and other record flowing through your integration. Failures are surfaced directly in the list — you don't need to dig for them.
For day-to-day monitoring, this is the fastest way to catch issues before they pile up. Open the Entities page, filter by entity type (Orders, Invoices, Articles, Stock), and look for any failed status indicators.
On notifications: AI-powered notifications are on the roadmap. We've deliberately avoided shipping generic "something failed" alerts in the meantime — in our experience they flood teams with context-free noise that gets tuned out fast. The goal is notifications that tell you exactly what broke, why, and what to do about it. Until then, the Entities view is the most reliable way to catch issues.
Use the Logs view to analyse over time
The Logs view is where you trace integration activity over a period of time — what synced, what failed, when, and why. It's the right tool when you need to understand patterns rather than individual records.
The most effective workflow:
Open the Logs page
Filter by status: Error
Narrow to a recent time window — last hour, last day, last week, depending on how often the issue appears
Review the failures for patterns, frequency, and common causes
This is especially useful for spotting things that have started failing recently. A configuration change, a new product type that breaks the sync, or an external API outage on one of your connected platforms will all show up here first.
Contact support when stuck
If after checking Entities and Logs you still don't understand what went wrong — or if the same error keeps recurring — contact support@junipeer.io.
To get the fastest and most useful response, include:
Order ID(s) or other entity reference(s) where the issue occurred
A detailed explanation of what you observed versus what you expected
Reproduction instructions if the issue is reproducible — what triggered it, what you did, what happened
Context about your integration setup — relevant settings, recent changes, anything that might be related
The more specific your support request, the faster the team can diagnose and resolve it. A task ID from the Logs page is the single most useful piece of information you can include.
For specific error codes and their resolutions, see the Error Codes reference. For common questions about how Junipeer works, see the FAQ.