Troubleshooting TGO Job Failure: “Unable to overwrite Task folder with processed temp processing folder”

📌 Problem

This error occurs during the final stage of SLAM Processing (TGO) processing when the system attempts to replace the Cycle’s POS/Task folder with the processed temp folder from the LP360 Working Directory. If the overwrite or move operation fails, the job ends with the error:

Unable to overwrite Task folder with processed temp processing folder

🔍 Root Cause

LP360 stages results in the LP360 Working Directory (default %TEMP%) and then moves them into the project’s Cycle POS folder. The error indicates that the move/overwrite was blocked due to one or more of the following:

• Insufficient disk space on either the Working Directory or the Project/Cycle drive
• File locks on the target folder (open Explorer windows or other processes)
• Antivirus/Endpoint Detection & Response (EDR) interference
• Path length or sync conflicts (OneDrive, Dropbox, etc.)

✓ Quick Checks

1. Verify free space
   Ensure both the LP360 Working Directory and the project drive have adequate space. Jobs can fail even if the project drive has space but %TEMP% is constrained.
2. Close open handles
   Close any Explorer windows or applications accessing the target POS folder. Use Resource Monitor → CPU → Associated Handles to identify locking processes.
3. Pause AV/EDR scanning
   Temporarily disable or add exclusions for:
   • LP360 Working Directory (default %TEMP%)
   • Project root and …\Cycle\POS\ folder

Immediate Fix

Scenario A — Salvage Completed Job

1. Locate the temp folder mentioned in the error (e.g., C:\Users\<User>\AppData\Local\Temp\TrajProc_<timestamp>).
2. Rename the existing POS folder to …\POS\TrajProc_<timestamp>_old.
3. Manually copy/move the temp folder into the POS location.
4. Refresh LP360; data should now be available even if the job shows as failed.

Scenario B — Rerun Cleanly

1. Move the LP360 Working Directory to a stable local path (e.g., D:\LP360_Work\).
2. Delete stale temp folders from the old Working Directory.
3. Apply AV/EDR exclusions and ensure target folders are closed.
4. Rerun the job.

Prevent Future Failures

• Use short, local NTFS paths for both Working Directory and Project folders.
• Apply permanent AV/EDR exclusions for LP360 Working Directory and project root.
• Avoid syncing tools (OneDrive, Dropbox) on active processing folders.
• Monitor disk space proactively on both drives.

Why It Happens

LP360/TGO relies on an atomic move from the temp processing folder to the Cycle POS folder. Any block—space, locks, or security software—prevents the overwrite and triggers this error.

If Issues Persist

• Collect the Job Manager log and the full path shown in the error.
• Validate contents of the temp folder; decide between manual promotion or rerun.
• Check %ProgramData%\LP360\Jobs\InProgress for corrupt job files (rare edge case).

📬 Need Help?

If you're still stuck, please Contact Support for assistance.