Sorry for taking a tangent here, but if this is the case, then using “Current User” should not be costing extra WUs as is highlighted in this post, right?
Been working with Bubble Support on a Work Unit question and found out something interesting. I use “Current User” information all over my app, as I bet everyone does. One example is I pass information on the Current User record to tons of SQL Connector calls. I reached out to Bubble Support because I had a very simple call to a MySQL stored procedure that was using 1.19WU. From my understanding, it should have cost about half so I created a bug to get some support. The Bubble Support Engineers …