Run with privacy rules and call the WF from the appropriate user. Alternatively, you can use the Data API to CRUD your records instead. These 2 are the only things that I can suggest without delving deeper into your setup (which unfortunately I don’t have the time for ATM).
As a rule of thumb, I will try to not do any searches in an action or nest searches. I usually build/adjust my datatypes around this rule.
For example, when it comes to API WFs initiated client side, I will try to grab the required data client side first, then pass them as parameters to the API WF.
In the backend, for example, if I know I will use a record for multiple actions, I will pass its values as a parameters to different Custom WFs depending on what I need done.
There’s no one solution. Just be aware of what costs WU.
3 Likes