Jitterbit · Private agents
Failed to find file in the local file store
Short answer
This Jitterbit transformation error means deployment metadata for a file did not fully sync from Harmony to the agent, which is usually transient. Re-run the operation. On agent 11.38 and later the metadata is restored on the next environment sync.
VerifiedLast verified
01Error text
Failed to find file in the local file store.
There is no file in the local file store. File_ID = ...02Likely causes
- A file's deployment metadata did not fully sync from Harmony to the agent, so the agent cannot find it at runtime.
- It can also follow exporting and re-importing a project between environments.
03How to fix it
- Re-run the operation. On agent 11.38 and later the metadata is restored on the next environment sync.
- If the same file keeps failing across runs on a current agent, contact Jitterbit support with the operation name and the TransformID and File_ID from the error.
04Official documentation
→Related errors
- Agent Not Running or UnreachableThis Jitterbit Studio message means the private agent services are not running or the agent host cannot reach the Harmony cloud. If the services are not running, start them. If a start fails, check the agent logs.
- Agent is incapable to process this messageThis Jitterbit ProcessEngine.log message means the agent has no free capacity, because every worker thread is in use or a capability metric reached its threshold. Review ProcessEngine.log for repeated capability status changes.
- Error 1720 or 1722 on Windows installationError 1720 or 1722 when installing the Jitterbit private agent on Windows usually comes from the bundled PostgreSQL, a missing Visual C++ Redistributable or leftovers from a previous agent. Install the 64-bit Microsoft Visual C++ Redistributable before the agent, and keep it installed.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries