I always saw charges for create a new thing or make changes to thing of 1.12 or 1.62 depending on user logged in status.
Now I’m seeing 1.93 for logged out user
Anybody else seeing higher charges?
@fede.bubble is this a known increase or a potential bug?
No way to answer this without seeing the configuration of your action
That action will cost you:
0.5 to make changes to thing
0.3 for a database search
0.6 for a workflow action
0.015 for returning a thing
= 1.415
so +small amount for bytes of data returned on the :first item Thing, that tracks with the 1.43 you see.
Switched the source of thing to change to current users field value that is related to another custom type and I see the drop, now just charged for the individual data request for the source.
In both situations the data thing to change was already used on page, both the search and current user field reference. I thought bubble used those already cached values for the action source if it was already in the page.
Is it that I’m not referencing the element on the page that already had the data as the action source that I get charged for secondary fetch when running action?
That’s true for expressions on a page, but not in workflows.
A page is a specific Bubble ‘context’, so is a ‘workflow’. Data that’s ‘already been fetched’ can’t be passed from the page to a workflow.
When you reference var - Invoice from a group data variable in a workflow, the unique ID of the invoice is passed to the workflow, and the workflow still needs to fetch that thing from unique ID (it just passes the unique ID, not the whole object).
Now there are some quirks to that of course. If you have some page data that is Get data from external API and it’s something like OpenAI's response message, then the entire API response is passed to the workflow basically as arbitrary JSON (because obviously you don’t want the workflow to re-run the API call). But if it’s a List of Things you’re passing, that’s a list of unique IDs. If it’s a list of thing:each item’s name, it’s a list of unique IDs (not a list of names) being passed to the workflow).
I’ve never seen the individual data request before when reference in workflow the current page thing or groups thing or current cells thing, at least not applied to WF action WU, maybe it was previously reported in data fetch and not attached directly to the WF in the charts breakdown report?
