---
title: SAP source troubleshooting
slug: o5nb3381
canonical_url: https://docs.coveo.com/en/o5nb3381/
collection: index-content
source_format: adoc
---
# SAP source troubleshooting
This page provides tools and information on how to troubleshoot issues with the SAP source.

## API call is unsuccessful

Your SAP [source](https://docs.coveo.com/en/246/) makes API calls to retrieve the application content.
If an API call is unsuccessful, the content is not [indexed](https://docs.coveo.com/en/204/), and the source logs the error in the [**Log Browser**](https://platform.cloud.coveo.com/admin/#/orgid/logs/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/logs/browser/)).

Symptoms:

* Coveo fails to index some or all of the desired content.
Items or metadata might be missing.

* Logs show error codes such as 401 or 403, which indicate that the API call was unsuccessful.

* Logs show messages such as `The page of items was empty for the offset...` or `The page of items was empty for the next page reference...`.

* The error message is not detailed enough to understand the cause of the issue.

To further investigate this issue, you can enable the logging of the response body and/or headers in the source logs when a call is unsuccessful.

> **Important**
>
> Depending on the API, the response body and/or headers may contain sensitive data that will appear in logs and therefore be exposed.
> Coveo automatically removes the `Set-Cookie` headers before logging, but custom headers may contain additional sensitive information.
> 
> We highly recommend you ensure that the response body and/or headers don't contain any sensitive data before logging them.

To log the response body and/or headers when an API call is unsuccessful

. On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, select your SAP source, and then click **Edit configuration with JSON** in the **More** menu.

. In the source JSON configuration, add `"LogResponseBodyWhenUnsuccessful": {"value": "true"}` and/or `"LogResponseHeadersWhenUnsuccessful": {"value": "true"}` to the `parameters` object.

. Save your changes.

. [Rebuild your source](https://docs.coveo.com/en/3390#refresh-rescan-or-rebuild-sources).

During the rebuild, Coveo will log the response body and/or headers of any unsuccessful call in the [**Log Browser**](https://platform.cloud.coveo.com/admin/#/orgid/logs/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/logs/browser/)).