🖌️ The Action That Remembered a Position, Not a Layer
An Action recorded while a specific layer is selected doesn’t actually remember that layer by its name or any stable identifier at all – depending on exactly how the selection step was recorded, it can instead remember the layer’s numeric position in the layers panel at the moment of recording, counted from the top or bottom of the stack. That distinction is invisible while replaying the Action on a file whose layer order happens to match the one it was recorded against, and becomes a real problem the moment the Action runs on a file where layers have been added, removed, or reordered, silently selecting and editing whatever layer now happens to occupy that same numeric slot instead of the one the Action was actually meant to target.
🔎 The Problem
Action recorded as: 1. Select Layer "Background Blur" (recorded while it was layer position 3 from the bottom in the source file's layer stack) 2. Apply Gaussian Blur, 12px 3. Set layer opacity to 85% What Photoshop actually stored for step 1 depends on how the selection was made during recording - a click directly on the layer's name in the Layers panel, versus a "Select Layer" menu command, can record either a name reference or a positional index differently across Photoshop versions and selection methods, and that recorded detail is not shown anywhere in the Action's own step list afterward. Run the same Action on a different file where a new layer was inserted above the original "Background Blur" layer, shifting everything else up by one position: Step 1 now selects whatever layer occupies the ORIGINAL numeric position - not "Background Blur" by name - and steps 2 and 3 blur and fade a completely different layer instead, with no error or warning that the wrong one was selected.
✅ Fix: Re-Record Layer Selection by Name, Not Position
- When recording an Action that needs to target a specific layer reliably, double-check the recorded selection step afterward by examining it (expand the step in the Actions panel) rather than assuming a click on the layer’s name was captured as a name reference by default.
- Where the Action is meant to run across many files with potentially different layer counts and orders, structure the file itself so the target layer has a unique, consistent name across every file the Action will run on, and verify the Action’s recorded step references that name rather than a position.
- For a batch of files with genuinely inconsistent layer structures, consider a scripted approach (an Action alone can’t reliably branch on layer name across arbitrary files) rather than trusting a recorded Action to generalize correctly across files it wasn’t originally recorded against.
⚠️ Why This Is Easy to Miss
- The Action runs to completion without any error on the wrong file, applying blur and opacity changes successfully, just to the wrong layer – there’s no failure to notice, only a result that’s visibly wrong once someone actually looks at the finished image closely enough.
- The Action can be used correctly for a long stretch of files that all happen to share the same layer order the Action was originally recorded against, so the positional-reference problem can go unnoticed for a long time and only appear once a file with a genuinely different layer structure runs through the same Action.
A recorded Action doesn’t necessarily remember what you meant to select – on a file with a different layer order, position and name can quietly stop meaning the same layer at all.

