Network Folder Source Connector – XML Data File Not Found

Network Folder Source Connector – XML Data File Not Found

Overview

When using Umango's Network Folders Source Connector with the option "Expect an XML data file with the same name as the importing file. If one exists, import the XML data", you may encounter import failures, particularly when larger files are being imported.

This article explains the cause and how to resolve the issue.

Symptoms

  • Documents fail to import from a watched folder
  • Errors indicate the XML file is missing or could not be found
  • The issue occurs more often with large files
  • Smaller files may process successfully

Cause

This issue is usually caused by a race condition between the document file and its matching XML file.

What happens is:

  • The external system places files into the watched folder
  • The document file arrives first
  • Umango detects the document and starts processing
  • The XML file arrives later
  • By default, Umango waits only 5 seconds for the XML file to appear
  • If the XML file does not appear within that time, Umango moves on and the issue occurs

This is more likely when:

  • Files are large and take longer to transfer
  • There is network latency
  • The source system writes the document first and the XML second

Resolution

Increase the time Umango waits for the XML file before it proceeds with processing.

Steps

  1. Open the Umango Dashboard
  2. Go to Advanced Configuration (see related knowledge article)
  3. Update or add the following setting:
Umango.Addin.Import.Folder.MaxWaitTime

Set the value in seconds. A good starting value is:

30

Save the configuration and test the import again.

  • Start with 30 seconds
  • Increase further if files are very large or the XML file is still delayed

Best Practices

  • Where possible, have the source system write the XML file first
  • Alternatively, have the source system write both files to a staging location and then move them into the watched folder only after both are fully written
  • Avoid dropping partially written files directly into the watched folder

Additional Notes

  • This behavior is by design so Umango does not wait indefinitely for a missing XML file
  • Increasing the wait time may slightly delay processing, but it improves reliability
  • This setting applies to folder-based imports that rely on matching XML files
Summary: If imports fail because the XML file is not found, especially for large files or batches, the XML file is likely arriving after Umango has already started processing. Increasing Umango.Addin.Import.Folder.MaxWaitTime usually resolves the issue.

    • Related Articles

    • How to Change the Temporary Working Folder in Umango

      Overview Umango uses a temporary working folder to store files during processing. This folder is separate from the batch folder and is used internally by the system while documents are being processed. In some environments, you may want to move this ...

    • Installing Umango Silently Using Command Line Properties

      This article explains how to install Umango without user interaction by running the installer from the command line and supplying MSI properties. The Umango installer is distributed as an EXE bootstrapper that contains an MSI package. For silent ...

    • Resetting The Umango Authentication Method

      Overview If the Authentication Method in Umango is misconfigured (e.g., an incorrect LDAP or MFA setup), administrators may find themselves locked out of the system. By removing the AuthenticationMethod entry from the database, Umango reverts to its ...