Diagnose stalled processing and export

What you will do

When an export seems stuck, use Export and Render History to find out whether it is waiting, still running, or has failed for a particular photograph. If a photograph failed, identify it before you retry. When the cause is a missing source file, you can restore that file, restart only the failed photograph, and confirm that Arams wrote the expected output.

Before you start

Leave the affected task in the history until you have identified the photograph and resolved the problem. The task details may be the only place where Arams shows the failure.
Keep your source photographs unchanged. Restarting a photograph from the history uses the original task’s destination, so look for the recovered file there.

Distinguish queued, running, and failed tasks

Open the project in which processing appears to have stopped.
Click the history icon above the photographs. Its tooltip is Export and Render History.
Find the newest task and read its status:
- Queued means the task is waiting. If another task is In progress, let that task finish first.
- In progress means Arams is processing the task. If you are unsure whether it is moving, compare its progress and elapsed time after a reasonable interval.
- A photograph under Failed to export needs attention. Waiting will not retry it.

Export and Render History with one Local Export task marked In progress at 0%. — If the task remains In progress, compare its progress and elapsed time after a reasonable interval before deciding that it has stalled. Arams 1.10.2 · Windows · American English

Export and Render History with an upper Local Export task Queued at 0% while the lower task is In progress at 49%. — Queued distinguishes a waiting task from the task already marked In progress. Arams 1.10.2 · Windows · American English

Read the error and identify the affected file

Expand Failed to export. Arams may show a red error indicator, a thumbnail, and a restart button without showing the filename or explaining the cause.
If a message names the cause, keep its exact wording and address that cause before retrying. Do not assume that every failure is caused by a missing source file.
If no filename appears, compare the thumbnail and failed-photo count with the photographs selected for the task. Return to the project if you need to check the selection. This identifies only the likely file, especially when several photographs look alike.
Check whether that source file is still at the name and path from which you imported it.

The task card can show Completed and 100% while its expanded details still contain Failed to export. Inspect the expanded photo section; do not treat the task-level percentage alone as proof that every file was written.

The screenshot below shows a failure caused by a source file that was no longer available at its imported path. A similar-looking failure may have a different cause. If Arams displays a message about a network service, plugin, account capability, credits, or a damaged file, follow that message rather than the missing-file procedure below.

A Completed 100% Export task with Failed to export expanded to show one thumbnail, a red error indicator, and a restart button. — Failed to export shows one failure even though the task card reads Completed 100%; this view does not display a filename or cause. Arams 1.10.2 · Windows · American English

Recover and verify the output

Use this procedure when the source file is missing from its imported path. For another error, correct only the condition identified by Arams.

Restore the source file under its original name at its original path.
In Failed to export, click the circular-arrow restart button on that photograph.
Wait for the task to return to work and then reach Completed and 100%. Expand its details and make sure Failed to export is no longer present.
In the task’s destination, open the newly written file and confirm that it is the expected photograph.

Export and Render History after recovery, with all three Local Export tasks marked Completed at 100% and no Failed to export section. — Completed and 100% with no Failed to export section means the restart has finished; open the expected file in the task's destination to confirm the recovery. Arams 1.10.2 · Windows · American English

Check the result

The recovery is complete when the task shows Completed and 100% with no Failed to export section, and the task’s destination contains the expected new file. The source photograph should remain at its imported path and unchanged. Do not rely on 100% alone: the failed state shown above can also appear on a task marked Completed and 100%.

If it still does not work

The task stays queued: look for another task marked In progress. Let that work finish before treating the queued task as failed.
The task stays in progress: compare its progress and elapsed time after a reasonable interval. Avoid starting repeated exports while the original task is active.
The task failed without a message: use the thumbnail, selection, photo count, and destination to identify the affected photograph. Do not assume a cause that Arams does not show.
The source file is missing: restore it to the same name and path used by the project, then restart the photograph from Failed to export. This chapter does not cover relinking a moved source through Arams.
The task completes but the expected file does not appear: check the task’s destination and filename settings, then open the newest output.
The message names a plugin, network service, account capability, or credits: keep the exact message; it identifies what needs attention or what to report to support. Restoring a source file will not address those failures. For plugin or credit availability, see Manage credits and plugins; for cloud processing, see Process photographs in the cloud.