Skip to main content
A record the customer can see in their HRIS is absent from Bindbee. The steps run cheapest first.
Before you start
  • You have something identifying the record: a name, work email, employee number, or the source system’s own ID.

​
Steps

1

Rule out your own filters

Fetch without filters and search the result before anything else.The usual culprits: an employment_status filter excluding a status you didn’t expect, a modified_after watermark from a run that already consumed the record, or a page walk that terminated early. See Pagination.Result: You know whether the record is absent or filtered out.
2

Check the sync ran after the record was created

A record created upstream after the last sync doesn’t exist in Bindbee yet - see Sync status.On a Development connector nothing syncs until you trigger it.Result: You know whether the data has had a chance to arrive.
3

Read the model's status on the last run

Read the run’s per-model breakdown. The status on the model you’re missing is the answer.Result: You know whether the model was loaded. Skipped and Not Supported settle it here.
4

Check permission

Many platforms answer a credentials gap with a filtered set, so a whole category of records goes silently absent.The signature is a model returning consistently fewer records than expected - see Origin-system errors.Result: You know whether the source system is withholding the record.
5

Check whether it's excluded upstream

The record may not be returned by the source system’s API at all: outside the scope of the report the integration reads, in a status the source excludes, or in a legal entity the credentials don’t cover.Query the source system directly through Passthrough to confirm whether their API returns it.Result: A definitive answer about where the record stops.
6

Check the logs

For a record that should have synced, the logs hold the request Bindbee made for that model and whatever the source system returned. See Logs.Result: Either the upstream response explaining the absence, or confirmation that Bindbee never requested it.

​
Records that were there and disappeared

Terminated employees. They stay in the response with a terminal status on most platforms. Where they vanish entirely, the source excludes terminated records from its API. Identifier changes. If the source reissued the record’s identifier, it may now be present under a different Bindbee id - see Duplicate records. File-based connectors. The file carries only what the customer’s export was set up to include, so a record you expect may never have been in it. Check the export’s scope with them before treating it as a sync problem.

​
Frequently Asked Questions

It synced but didn’t map to a unified record: a required field the unified model needs is absent upstream. Report it with the connector ID and the raw payload.
Connectors are independent, and credentials differ in the populations they cover.
That’s reconciliation rather than a missing record - see Record counts.
  • Sync status - the per-model breakdown that answers most of these
  • Duplicate records - when a record appears twice instead of not at all
  • Scoping - the reasons data is absent with no error