Loading

Data 360: Troubleshooting SFTP Data Stream Ingestion Errors

Publish Date: Dec 4, 2025
Description

Accessing Download Log

When an SFTP data stream errors during refresh/ingestion, the Last Run Status can show as Error or Failure. More information on the exception that caused the error is available by following these steps:

  • Open the Data Stream and click Refresh History.
  • In the Refresh History table, click the red error symbol in the Status column.
  • The Error Details popup can show an error code, such as STREAM_JOB_STATUS_FAILURE. Click the Download Log hyperlink to access more details.

Review the table below for more details about the exception in the log file.

Resolution

Common Errors

ErrorFull Exception ExampleDescriptionSteps to Resolve
Data read has a different length than the expectedException while uploading data using com.salesforce.dataconnectors.datawriter.ObjectStoreWriter$ObjectStreamProviderHelper - Data read has a different length than the expected: dataLength=201247; expectedLength=361467; includeSkipped=false; in.getClass()=class com.amazonaws.internal.ReleasableInputStream; markedSupported=false; marked=0; resetSinceLastMarked=false; markCount=0; resetCount=0This exception has been observed when more than one .zip file is present in the SFTP directory matching the data stream's ingestion criteria.See Data 360: SFTP Data Stream Failing with Error: "Data read has a different length than the expected" for more details.
Network unreachablecom.salesforce.dataconnectors.api.exception.ConnectorException: java.sql.SQLException: System error: SOCKS: Network unreachableIndicates a network issue preventing the ingestion job from completing successfully.

Check if your SFTP server has an IP allowlist. See IP Addresses Used by Data 360 Services for the list of Data 360 IPs that need to be allowed. 

No data was found during extractionNo data was found during extraction

A file was not found in the SFTP directory at the time of the refresh. If the setting "Log an error if no file is found" is enabled fo the data stream then an error is shown in the Refresh History. See Data Stream Settings and Refresh Modes for information about this setting.

Edit the data stream and disable "Log an error if no file is found" if no file in the SFTP directory should not log an error. Review the scheduling of your data stream to ensure it runs after the process to add the file to your SFTP server completes.
Total extraction size [file size in bytes] bytes exceeds the maximum limit of [limit in bytes] bytescom.salesforce.dataconnectors.api.exception.ConnectorException: Total extraction size 32339727802 bytes exceeds the maximum limit of 32212254720 bytes The total size of the files being ingested in a single run is greater that the allowed limit. Check your SFTP server to review the size of the file or files that are present. 

Reduce the total size of all files being ingested per data stream run to below the maximum limit listed in the exception. Review Data 360 Limits and Guidelines for the documented limit 'Maximum data per data stream run'. Note: the documented limit may be lower than the limit mentioned in the exception.

Unable to position the currentPosition from -1 to 0Exception while uploading data using com.salesforce.dataconnectors.datawriter.ObjectStoreWriter$ObjectStreamProviderHelper - Unable to position the currentPosition from -1 to 0SFTP servers often enforce limits on the number of simultaneous connections allowed per user or connection. If multiple data streams are scheduled to run at the same time using the same SFTP connection, this can exceed the server's connection limit, resulting in errors and failures. Follow best practice advice in Data 360: Best Practices for Managing SFTP Data Stream Errors Due to Scheduling Conflicts and Connection Limits

If you are seeing an error that is not mentioned in this article or the suggested steps do not resolve the issue, create a case with Salesforce Support for further assistance.

Intermittent Errors

Occassionally, a one-time error may be observed in the Refresh History of an SFTP data stream and then subsequent ingestions complete successfully without any action being taken. This type of intermittent error may indicate a temporary issue that is automatically resolved when the ingestion is retried. If you can see in the Refresh History that a data stream is consistently ingesting successfully after a one-time error occurred then no action to mitigate that intermittent issue should be required.

Knowledge Article Number

004947530

 
Loading
Salesforce Help | Article