Troubleshooting the folder upload module

A file never shows up in the session

Cause. The file was created outside the module’s watch window: before the session started, or after the DelayBeforeUpload grace period following session end had already elapsed. Both are by design; see Timing.

Fix. Confirm the file’s creation time falls inside the window. If the source writes late, increase DelayBeforeUpload.

A file is missing and the log shows a read error

Cause. The file was still open, or locked by whatever created it, when the module tried to read it at the end of the delay window:

Error reading file: {FilePath}

The module does not retry a locked file; it is skipped for that session.

Fix. Make sure the writing process has closed the file well before DelayBeforeUpload elapses. Increasing the delay is the only lever this module gives you; there is no separate retry setting.

The watched folder was recreated on startup and is empty

Cause. The configured Folder did not exist when the module initialised. This is expected, not a fault:

Folder Upload folder does not exist: {Folder}. Creating it.

The module creates the folder and continues; nothing already written to a previous location is picked up.

Fix. Point Folder at the path the writing process actually uses, and confirm both HEAT Capture and that process can reach it: a network path that only one of them can resolve behaves identically to a missing folder.

No files are captured at all, even inside the window

Cause. The module could not create its file watcher, most often because the configured Folder became inaccessible between initialisation and session start (removed, or a network path that dropped):

Error setting up file watcher

Fix. Confirm the folder is reachable, then start the session again. If the module keeps failing to start, see Manage capture modules for how HEAT Capture retries a module that fails to start.

HEAT Capture team. Last updated 2 October 2026.