How should I make a Photoshop batch action stop when a product file has a different layer structure?

Set up a controlled pilot

Choose two product files whose relevant layer structure matches the action’s assumptions, plus one test copy with a deliberately different structure. Keep the approved originals out of the pilot’s output destination. This is a manual validation exercise, not a claim that Photoshop can identify the mismatch for you.

Illustrative exercise: File One and File Two have the expected product image layer and background arrangement. File Three has an extra layer that changes which layer would be affected by the recorded edit. The action may run without reporting that structural difference; the pilot must catch it by inspection.

1. Select the intended action and a source that contains only these test copies. In Photoshop’s Batch options, choose a destination folder rather than Save and Close, which overwrites originals.
2. If the action contains a recorded Open command that could replace the selected source files, enable Override Action Open Commands. Leave it off only when the action deliberately requires fixed files.
3. Give output files a naming scheme with at least one unique element so processing does not overwrite another file.

Insert a deliberate checkpoint

In the Actions panel, select the command after which Photoshop should pause, or select the action name to place the stop at its end. Use the panel menu’s Insert Stop command, enter a message that tells the operator what to inspect, and confirm. The stop is a human checkpoint: it does not compare layers or decide whether a document is structurally valid.

At the pause, inspect the active test document’s layer structure and confirm the intended target before continuing. Photoshop’s Play resumes after the manual work. A Continue button can be included in the stop as a reminder, but it does not turn the check into automatic validation.

1. For this pilot, write a stop message such as: “Confirm the product image layer and background arrangement before continuing.”
2. On File One and File Two, verify the intended layer is the one the next action step will affect. Continue only when that observation matches the action’s assumptions.
3. On File Three, if the structure differs or the target is ambiguous, do not continue the structure-sensitive step. Stop that file’s path and record it for review.

Choose an exception route

A pause can guide a person, but it cannot automatically send a mismatched document to an exception folder or skip only that file within the batch. Treat the routing as a manual process: at the checkpoint, halt or otherwise end the batch, keep the mismatched file out of the approved-output set, hold it for review, and rerun the matching files separately. Note the observed discrepancy and review it separately. The practical acceptance condition is that matching files finish as expected, while the mismatched file is neither silently accepted nor published as approved.

Do not confuse the manual stop with Batch’s error controls. Stop for Errors stops processing when Photoshop encounters an error; Log Errors to File records errors. Neither is documented as checking SKU identity, layer names, or layer arrangement. A file can therefore have the wrong structure without triggering an application error.

1. If the mismatch is found at the stop, do not resume past the risky edit. Halt or otherwise end the batch at the checkpoint, mark the file as needing structural review, hold it out of approved output, and record the visible reason, such as an unexpected extra layer or an unclear target. Remove or hold the mismatched file before rerunning the matching files separately.
2. If Photoshop reports an actual processing error, choose Stop for Errors when you need processing to halt, or Log Errors to File when you need an error log. Treat either outcome separately from a structural mismatch.
3. After correcting or manually adapting the exception on a separate copy, inspect its result before adding it to approved output.

Accept or reject the pilot

Pass the pilot only if File One and File Two complete as intended, File Three is identified for review before it can be approved, and the reason for review is recorded. If the mismatch reaches the output without being noticed, the checkpoint did not work as an operational control: revise the stop message or inspection procedure and repeat the pilot with fresh copies.

For real batches, choose the source deliberately: Photoshop can use a folder, imported files, opened files, or Bridge. Include All Subfolders expands the input scope, so leave it out unless subfolders are part of the intended batch. If a recorded Save As path would direct output elsewhere, Override Action Save As Commands makes the selected batch destination take precedence. These controls manage file selection and saving; they do not validate document structure.

Use this question’s review worksheet

The sample rows are fictional exercise data. Preserve the example, save a working copy and record your own inputs, observations and decisions. The example is not a test receipt.

Fictional manual pilot record (CSV)