Hi all,
one of the table is consuming too much WUs , there are multiple fetch/update queries running for this table named as “vehicles” , upon clicking the pie chart to dig deeper into exact expression/action/event i end up at the table always and not at the exact culprit which is causing this much of WUs , do you guys have any idea how can i find the exact expression/action/event that is causing the WUs spike?
Do you have Database trigger events associated with that datatype?
Yes , but that too is handled conditionally. So IG it is hardly contributing to WUs.
The database trigger events are triggered regardless of any conditional you place in the workflow. The conditional only prevents that further actions are taken.
Each database trigger event consumes 0.05 WU, sadly.
You can try adjusting the privacy rules for the “vehicles” table. By limiting the data being fetched (e.g., removing unnecessary columns or restricting rows based on specific conditions), you can reduce the amount of data being processed, which in turn can significantly lower WUs. For example:
- Remove fields that aren’t needed for the current view.
- Restrict rows based on conditions that are relevant to the current user or context (e.g., only showing vehicles related to the logged-in user).
Additionally, sometimes the issue isn’t just how much data you’re fetching, but how often data-related events (like auto-binding or repeating groups) are triggered. You can use the ‘App search tool’ to see all the places it’s being used.
1 Like
thanks @igor.le.nascimento @ademiguel