When the JT Engine processes flat (ASCII) file imports, it relies entirely on the accuracy and completeness of the file path provided in the Planned Event configuration. If the path is incorrect, incomplete, or missing key components, JT Engine may return a “File Not Found” error during execution. This behavior is typically linked to file name or extension issues, rather than service-level access problems.
Cause
A “File Not Found” error most commonly occurs when the file path supplied in the Planned Event does not accurately reference the target file. Two scenarios tend to cause this issue:
- The file name is incorrect
- The file extension, such as .csv or .txt, is missing
Flat files must include their full name and extension. If the extension is omitted or the name is mistyped, JT Engine cannot resolve the file path and therefore cannot locate the file.
Resolution
To ensure successful imports, the file path specified in the Planned Event must be complete and precise. The following steps typically resolve the issue:
- Verify that the correct file name is provided
- Confirm that the file extension is included and matches the actual file type