When you use an action as a line of code in a script element within a workflow, the action links do not show their usage. This issue results in workflow validation failures, as automated cleanup processes incorrectly identify the active actions as unused and delete them via API calls.
A regression was introduced via a recent regex update for scripting. The regex incorrectly interprets $ and \ as replacement metacharacters, which causes the entire workflow to be ignored during usage parsing.
This issue is under review with Broadcom Engineering. Subscribe to this knowledge article to get updates on this issue.
Workaround:
To temporarily resolve this issue, do not use $ and \ directly in your scripts. Place them in variables instead by following these steps:
'$select=name') as its value.After implementing these changes, "Find Dependencies" will begin working from the workflow, and "Find Usages" will function properly for the actions used inside.