Overview
The Logs page provides a detailed audit trail of everything that happens during your syncs. Each log entry records a specific event — such as a successful record export, a warning about missing data, or an error that prevented a sync from completing.
You can find the Logs page in the left sidebar of any integration.
Log table
The log table shows the following columns:
Created — the date and time the log entry was recorded. Displayed in the format YYYY-MM-DD HH:MM.
Message — a human-readable description of what happened. Messages typically describe what was attempted and whether it succeeded or failed, for example loading a record, exporting an entity, or encountering a validation issue.
Flags — additional context or details about the event. May contain bullet-pointed error descriptions or technical details.
Reference — the record ID associated with this log entry (e.g., an order number, article number, or customer ID). Use this to locate the specific record that triggered the log.
Status — a color-coded badge indicating the severity:
success (green) — the operation completed without issues
info (blue) — an informational message, no action needed
warning (yellow) — something unexpected happened but the sync continued
error (red) — the operation failed and may need attention
Each log entry also includes a View task link that takes you to the Task that generated the log entry.
Filtering logs
Use the filter fields at the top of the log table to narrow down results:
Status — dropdown to show only entries with a specific status (e.g., only errors).
Message — text search to find logs containing specific words or phrases. Useful for searching error messages.
Reference Number — search by a specific record ID (order number, article number, etc.) to see all logs related to that record.
After setting your filters, click Apply to update the results.
Exporting logs
Click the Export to CSV button at the top of the page to download all log entries (respecting current filters) as a CSV file. This is useful for:
Sharing log data with Junipeer support when troubleshooting
Archiving log history
Analyzing patterns in errors over time using a spreadsheet
Understanding log messages
Log messages generally fall into a few categories:
Record not found — the sync tried to look up a record (an article, customer, or order) in the target platform, but it did not exist. Check that the record has been created in the target system, or review your field mappings in Settings.
Connection or timeout errors — the target platform did not respond in time. This is usually temporary. Try again later, and if it persists, check the platform's status page or your Connector credentials.
Rate limit errors — too many API calls were made in a short period. Consider reducing your sync frequency in Scheduling.
Validation errors — a record could not be created in the target platform because required data was missing or invalid (e.g., a missing customer name or unsupported currency). Review the error message for details and adjust your settings or source data.
For platform-specific error codes and resolutions, see the Error Codes page.
Tips
Check Logs regularly after making configuration changes to catch issues early.
Use the Reference Number filter to trace the full history of a specific record across all syncs.
If you see many errors with similar messages, the cause is likely a configuration issue in Settings rather than a problem with individual records.
For critical integrations, consider setting up notification rules to get alerted when errors occur. Contact Junipeer support for help configuring notifications.