Data Lake Sync Error: HTTP 408 Timeout When Reading Data

Overview

If Data Lake Sync fails with a logged error referencing HTTP Status: 408 while extracting data from the Infor Data Lake, the most common cause is that the underlying Infor API request has timed out before the data could be returned.

This issue typically occurs when the Data Lake table has become fragmented, contains stale data, or the Infor Data Lake service is unable to return the requested dataset within the allowed response time.

Symptoms

You may see one or more of the following:

• Data Lake Sync job fails with a HTTP Status: 408 error
• Table synchronization fails repeatedly
• Initial table loads do not complete
• Incremental loads stop processing data

Cause

Data Lake Sync retrieves data through the standard Infor Data Lake APIs. A 408 error indicates that the Infor API did not return a response within the allowed timeout period. Because the timeout occurs within the Infor platform, Data Lake Sync cannot complete the extraction. In most cases, the affected table must be rebuilt within the Infor Data Lake.

Resolution

The recommended resolution is:

1. Purge the affected table from the Infor Data Lake using Infor OS > Data Fabric > Purge
2. Republish the table from the ERP system to the Infor Data Lake.
3. Wait for the republish process to complete.
4. Allow the Data Lake Sync job to process.

Republishing the table allows the Infor Data Lake to rebuild the underlying data set, which typically resolves the timeout condition.

How to Republish a Table

The exact republish process varies by ERP application and Infor product. Please refer to the ERP-specific republishing instructions documented elsewhere in this Help Center.

Note: The table must be fully republished and available in the Infor Data Lake before rerunning Data Lake Sync.

If the Issue Persists

If the 408 error continues after the table has been purged and republished:

1. Verify that the republish completed successfully.
2. Confirm that the table is visible and queryable within the Infor Data Lake.
3. Contact Orange Query Support and provide:
   • The table name
   • The Data Lake Sync connection name
   • The timestamp of the failed synchronization
   • A copy of the error message

Our team can help determine whether the issue is related to the Data Lake table, the Infor API, or another environmental factor.

Additional Information

A 408 timeout is generated by the Infor API layer and does not indicate a problem with the Data Lake Sync application itself. Data Lake Sync can only process data that is successfully returned by the Infor Data Lake APIs.