Troubleshooting data errors

When a reference data endpoint is not returning expected data, you can carry out a number of steps to find out what's causing the issue.

Confirm the data is not being filtered out

Attempt the call again without any filtering that may be in the current request. Some data endpoints also have optional flags that include data that would otherwise be excluded. If this larger set of data includes the data you were expecting, determine which filter removes the data and whether this is valid for the data in question.

Confirm your client has access to the data

The Identity Endpoint provides the sales channel for the current client. Confirm with your circuit administrator/downstream applications that the expected data is available for the given sales channel.

Check trace logs

You can request your Connect administrators to enable trace logging for Connect, or pass the Trace Logging Token with your request. A number of data endpoints that filter a large set of data have extensive trace logging implemented, specifying which data has been filtered out and why.

Confirm the data is in the connect database

If you have access to the Connect database, confirming that the expected data is in the database can help diagnose errors that are outside of Connect. If the database does not contain the expected data the issue will most likely need to be fixed in the Connect Web Loader or in downstream applications.