Troubleshooting: Agisoft Ortho Mapping (MfE or MfEC) Job Stuck in “InProgress” With No Errors

📌 Problem

An Agisoft Ortho Mapping (MfE or MfEC) job starts successfully but remains in InProgress indefinitely until manually canceled or LP360 is closed. The job log shows only early initialization steps (project save/load and GPU detection), with no photo alignment, DEM usage, or ortho generation stages logged.

Example log output may end similar to:

SaveProject: …
LoadProject: …
Vulkan device Intel(R) Arc(TM) Pro Graphics: no pci bus info extension
Found 2 GPUs …

No explicit error message or Python traceback is reported.

✅ Probable Resolutions

1. Verify Agisoft Metashape Console License Activation

   Agisoft Ortho Mapping requires an Agisoft Metashape Console (Ortho Mapping) license to be activated on the machine running the job. If the license is missing or inactive, the job may launch but stall without reporting a failure.

   1. Open LP360 Drone
   2. Go to File > Project Settings
   3. Open the EXP tab
   4. In the Agisoft Ortho Mapping section, select Check Activation Status

   If Metashape is not active, activate the correct console license and re-run the job.

   ---

2. Test Whether Email Notifications Are Blocking Job Completion

   LP360 Job Manager workflows (including SAfE, MfE, and MfEC) invoke the internal notification function only if a valid notification email address is configured.

   If the notification email address is None, empty, or set to x or X, the notification function returns immediately and no SMTP call is attempted. The job will continue to run normally, but no begin or completion email notifications will be sent.

   This behavior can be used as a diagnostic test to determine whether outbound email notifications (SMTP / firewall configuration) are contributing to a job remaining in an InProgress state.

   To perform the test:

   1. Open LP360
   2. Go to Project Settings → Global → LP360 Email Notification Settings
   3. Set the notification email address to None, leave it blank, or set it to x, or X
   4. Apply the changes and re-run the job

   Interpreting the result:

   • If the job completes successfully, this indicates that email notification handling (SMTP connectivity, firewall rules, or port configuration) was likely preventing job completion.
   • If the job remains stuck, the issue is unrelated to email notifications and other causes should be investigated.

   Learn more about configuring Exceptions for LP360 Email Notifications

   ---

3. Outbound Email / Firewall Port Configuration (SMTP)

   In some environments, jobs can remain in InProgress if outbound email or notification traffic is blocked or misconfigured at the firewall level.

   This has been observed when SMTP services (such as SMTP2GO) are configured to use a different port than what is permitted by the organization’s firewall. In these cases, the processing workflow may start normally but never signal completion back to LP360, leaving the job stuck in an active state without producing an error.

   To validate:

   • Confirm which SMTP service is in use (for example, SMTP2GO)
   • Verify the SMTP port configured by IT matches the ports allowed on the firewall
   • Ensure outbound connections on the configured SMTP port are permitted from the LP360 machine

   If the firewall is blocking or redirecting the configured SMTP port, update the firewall rules or SMTP configuration accordingly and re-run the Ortho Mapping job.

   Learn more about configuring Exceptions for LP360 Email Notifications

   ---

4. GPU Backend Initialization Stall (NVIDIA GPU Confirmed)

   On some systems, LP360 correctly selects the discrete NVIDIA GPU, as confirmed by the application diagnostics (for example, the About LP360 dialog reporting an NVIDIA renderer). In these cases, the job stall is not caused by the integrated GPU being used.

   Instead, the stall occurs after GPU selection, during Metashape’s internal GPU backend initialization phase. This can include CUDA, OpenCL, or Vulkan setup performed by the Metashape console engine before active processing begins.

   When this occurs:

   • The GPU is detected and reported correctly
   • No alignment, depth map, DEM, or ortho steps begin
   • The job remains in InProgress with no error output

   LP360 does not provide a supported option to disable GPU acceleration or force CPU-only processing for Agisoft Ortho Mapping jobs. As a result, GPU backend issues must be isolated through environment testing rather than configuration changes.

   Recommended isolation steps:

   • Run the same project on a different machine with a different NVIDIA GPU model or driver version
   • Update or roll back the NVIDIA GPU driver to a known stable release
   • Test the workflow without a DEM or with a reduced photo set

   If the project completes successfully on another machine, this indicates a Metashape GPU backend compatibility issue rather than a licensing or LP360 configuration problem.

   ---

5. Validate Input Data

   To rule out data-related causes:

   • Run the job without a DEM
   • Test using a small subset of retained photos
   • Confirm all photo paths are accessible and stored locally

   Large photo sets or specific DEM configurations can prevent the workflow from advancing without producing an explicit error.

   ---

6. Clear Stuck Job State

   If the job cannot be canceled or deleted from Job Manager:

   1. Close LP360

   2. Navigate to:

      %ProgramData%\LP360\Jobs\InProgress

   3. Delete the folder corresponding to the stuck job
   4. Restart LP360 and resubmit the job

   This clears orphaned job state that can prevent subsequent jobs from executing correctly.

   ---

📚 Additional Notes

When an Agisoft Ortho Mapping job stalls in InProgress with logs stopping at GPU detection, the failure occurs before active processing begins. While GPU backend compatibility is a common contributing factor, resolution typically requires environment isolation rather than configuration changes within LP360.

📬 Need Help?

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