How do I read and search logs?

Updated 5 days ago

Open a connector in the dashboard and go to its logs to see every request we made to that customer's system and what came back. You can also open Logs from the main menu for your whole account, but starting from the connector is faster because it only shows that customer's requests.

Logs are the last step in troubleshooting. Check the connector's sync status first: most questions are answered by the per-model breakdown of the last sync, without opening a single log entry.

What a log entry shows

Field	What it holds
Direction	`READ` or `WRITE`
Connector	The customer connection the request belongs to
Endpoint	The path we called, on Bindbee or on the source system
Status	The response code, and the error code where there is one
Request and response	The full bodies. Open an entry to expand them

Read the source system's response body first. We keep it exactly as the source system returned it, and it usually names the permission or field that caused the failure.

Find the request you need

Open the connector's Sync tab and note when the run you're investigating started.
Open that connector's logs and load entries back to that time. Entries are listed newest first.
Look at the entries for the model in question, for example READ entries on the benefits endpoint when benefits are missing.
Open the entry and read the response body.

Question	Where to look
Why is this connector not returning a model?	`READ` entries for that model's endpoint. A `403` means a permission gap. No entry at all means the model is out of scope
Why did my write fail?	The `WRITE` entry, then the source system's response body
Why is a record missing?	The `READ` entries for that model

What you won't find in the logs

Models marked Skipped or Not Supported. We never requested them, so there's no entry. The connector's sync status explains both.
A field that came back empty. A 200 with a missing field leaves nothing to find. That's scope, a permission in the source system, or the unified model.
A record deleted in the source system. A deletion produces no request.
Workday RaaS report data. For a RaaS connector, the logs show the token request at the start of each sync. The report itself is fetched as a streaming request from its report URL, which isn't logged. Everything the report returns for a worker is stored in that worker's raw_data, so check there to see exactly what came through.

Logs are dashboard-only

There's no API for connector logs. For monitoring in your own systems, use sync webhooks or the connector's status and sync_status fields from Get Connectors.

Webhook delivery logs are separate. They record our attempts to reach your endpoint, live under Logs on the Webhooks tab, and do have an API: List Webhook Logs.

Was this helpful?