How does the DLA Autoload process determine when to run, and what should be checked if the DLA batch does not execute or fails?

    How DLA Autoload Trigger Works

• The DLA automation job checks the last modified date of the source files on SFTP.
• The DLA batch is triggered only when:
  • A new source file is uploaded, or
  • The existing source file’s modification timestamp is updated
• If no file modification is detected after the last successful processing time, the DLA batch will not run again automatically.

    Important Clarification About Supplier Normalization

• Supplier normalization completion alone does not automatically trigger a DLA batch rerun.
• Even if supplier normalization activities are completed in the backend:
  • The source file timestamp must still be updated, or
  • The file must be re-uploaded to SFTP
• for the changes to be processed during the next DLA execution.

    Ways to Trigger DLA Reprocessing

• To rerun the DLA process and reflect updated data in the portal, users can:
  • Re-upload the same source file to SFTP
  • Modify the existing file’s last modified date
  • Request Customer Support to manually trigger the DLA batch after updating the source file timestamp

    Common Reasons Why DLA Autoload Fails

• Missing Mandatory Columns in Source File
• If mandatory columns are missing in the uploaded source files, the DLA Autoload process may fail.
• Example:
  • Missing required columns in CSV files
  • Incorrect header names
  • Header/data row formatting issues
• Users should validate source files carefully before upload.    

    Best Practices for Successful DLA Processing

• Ensure all mandatory columns are present in the source files
• Avoid modifying file structure unintentionally while opening/editing files
• Use validated or cleaned source files whenever possible
• Update the file timestamp when reprocessing is required
• Verify SFTP uploads are completed successfully
  

    Email Notification Behaviour

• DLA success/failure notifications are generally sent to the configured Primary CSM for the org. If notifications are not being received, verify that the correct user is configured as the Primary CSM.