Logs

The Logs page is the raw, chronological stream of everything your integration has repoted. Where the Tasks view groups events into discrete executions, the Logs view flattens them into a single time-ordered feed across all tasks. This is the tool you reach for when you need to answer "what has this integration been doing lately?" and "what went wrong when?"

What Logs shows

Every log line produced by every task is visible here — successes, informational notes, warnings, and errors, all interleaved in a single list.

Each row has:

• Created — precise timestamp of the log line

• Message — human-readable description of what happened

• Flags — internal markers (rarely needed for troubleshooting)

• Reference — the entity ID this log line applies to, when relevant

• Status — success, info, warning, or error

• View task — jump to the parent task that produced this line

The list is paginated and orders newest first by default.

Logs and other views

Here is a distinction between general logs and other reports in Junipeer system:

1. Tasks - "What runs happened and how did each one go?"

2. Entities - "What is the current state of this specific record?"

3. Logs - "What was said, in what order, across everything?"

Export to CSV

The Export to CSV button at the top downloads the current filtered view as a spreadsheet. Use this when:

• Attaching to a support ticket for offline analysis

• Reviewing a large window of activity in Excel or Google Sheets

• Sharing findings with your accountant or a colleague who doesn't have Junipeer access

The export honours your current filters — apply the filters first, then export the narrowed set rather than the full log stream.

Tips

• Errors first, everything else later. The single highest-leverage filter is Status: error. Start there before scrolling anything

• When reporting issues to Junipeer Support, make sure to prepare all relevant IDs. You can also send the URL to specific, erroneous Task.

• Reference filtering beats scrolling. If you know the order ID or invoice number, filtering by Reference gets you to the truth much faster than scrolling by date

• View task is one click away. Every log line links to its parent task — if the log entry looks interesting, jump to the task for the full context including inputs and statistics

• The absence of errors is a valid finding. Sometimes the useful conclusion is "no errors happened in this window" — which tells you the problem was upstream or downstream of Junipeer, not inside it