The meaning of my script is that it searches and launches an action, depending on the name of the document / specific layer. That is, problems with hard-coded action names simply do not arise - they are determined dynamically during the script. If you run the script from the automation menu, it is executed outside the context of the action panel (that is, when the action is executed, the command cursor stops after the stop command and the user can continue the action with a hotkey or play button). However, in this case, I have to show the script interface every time so that users can specify the launch parameters they need. To avoid displaying the interface, users write it to the action panel as a separate operation - in this case, Photoshop considers the action from which the script is run as “parent” in the action chain and, if there is a stop command (completely stopping execution), returns the cursor to the action from which the script was run. So far, I have recommended that users break down the actions into separate steps and not use the stop command. However, I am trying to find a solution to this problem.
... View more