Troubleshooting
Eloqua’s bulk API includes endpoints to help you troubleshoot your imports and exports. Specifically, these endpoints provide insight into what happened during the sync phase of an import or export.
To control for different data access permissions, Eloqua
associates imports and exports with the user who creates them. Only the user who synchronizes an export is able to retrieve the
exported data: any other user who attempts to retrieve it will
receive an error.
To retrieve data for a given export definition, resync that data yourself and then retrieve it.
View sync logs
Sync logs provide aggregate data detailing what happened during a specific sync. Unlike the sync's status field, which simply indicates success, failure, and errors, the /syncs/{id}/logs endpoint response includes the Eloqua status codes and a human-readable message.
For example, calling
https://<host>.eloqua.com/API/Bulk/2.0/syncs/1196/logs yields:
{
"count": 3,
"hasMore": false,
"items": [
{
"count": 4149,
"createdAt": "2014-05-12T14:23:05.9100000Z",
"message": "Successfully exported members to csv file.",
"severity": "information",
"statusCode": "ELQ-00102",
"syncUri": "/syncs/1196"
},
{
"count": 0,
"createdAt": "2014-05-12T14:23:07.2670000Z",
"message": "Deleted internal staging for data transfer.",
"severity": "information",
"statusCode": "ELQ-00131",
"syncUri": "/syncs/1196"
},
{
"count": 0,
"createdAt": "2014-05-12T14:23:07.7630000Z",
"message": "Successfully converted csv file to sqlite, taking 264 kb.",
"severity": "information",
"statusCode": "ELQ-00106",
"syncUri": "/syncs/1196"
}
],
"limit": 1000,
"offset": 0,
"totalResults": 3
}
This provides more granular information and can help you debug where an unsuccessful sync went wrong.
Check for import errors
The /syncs/{id}/rejects
Eloqua performs validation on some data. If you attempt to import a non-valid email address using the bulk API, that record will be rejected. The /syncs/{id}/rejects endpoint allows you to see what records were not imported, so that you can correct any issues and try again.
Retrieve past data files
In some cases, you may choose to reuse an export definition. For example, if you are
performing routine exports, reusing an existing definition can save time and effort. However, when you resync the export, the exported data may have changed. Last week's output from /contacts/exports/123/data may be different from today's.
The /syncs/{id}/data endpoint enables you to retrieve the data associated with a specific sync. This can be useful to retrieve past data or debug issues retroactively.