I’m having an issue in an app using the “is on the last page” state.
But in my case when I use ≥ and ≤ to filter the created date of the items on the repeating group it brings 400 items, when I use > and < it brings only 10 (the repeating group is limited to 10 rows), (the date of the items are not equal to the start or end date).
I did an isolated test in this video. I couldn’t recreate my case, but found out that using the is in the last page condition brings a lot more data and consumes more WU.
Yikes… seems like a good case for using hidden pre-loading RGs.
Going to have a look at this today, though I have to say I have seen a large uplift in wu consumption recently. A lot of workflows that I’ve had in place for the lifetime of our app suddenly became so cripplingly expensive that I had to change them.
I’ve been almost hitting our wu cap of 1.2m every month for the last few months, after consistently being somewhere closer to 400k previously
@geovanevasconcelos2 my plugin Data Jedi can help with that. I’ll be adding the paginator element to the plugin this week.
@ed19 what are some of those areas that are consuming the most WUs? If it is searches or creation of large amounts of data Data Jedi can help reduce them by 95-99%. If it is comparing lists of the same data there is a SS action in the plugin that compares two lists and outputs four (unchanged, modified, new and updated list).
Very interesting, will take a look at this for sure!
It seems to be random if I’m honest, like bubble has decided my wu quota and randomly spikes a workflow to meet it. I know it’s around the same time as a lot of other users experiencing wu spikes, so I’ve put it down to that (still sat fairly comfortably in our limit too, so it’s not become a massive issue just yet).
I’d reach out to bubble support just to let them know, so they could take a quick look. There have been a couple of reported incidents involving Bugs and WUs with usage spikes.
