Workflow unit guzzling up app in trivial activity

Need help
1

I am failing to understand that Uploading a picture costs 0.3 workload unit, adding it to a Thing using Make changes to a thing costs 6-7 WU

Same for many other minor event that guzzle up Workload Units like water.

Creating a Audit trail with the following parameters:
User: Current User
Lab: Current Lab
Activity: Image Uploaded
Menu Option: Eg Bill Desk ( comes from option set)
Activity type: Registration ( comes from option set)

this is causing 17-18 WU?? Is it usual or I am doing something wrong.

Is pulling data from Option set the reason for such WU consumption?

Please help

2

Are you doing any searches when creating that Audit Trail? Can you share screenshots of the action and the entire workflow? Seems very strange.

If you remove the image upload from the creating audit trail, does the WU usage for that action return to a normal amount?

3

Screenshot 2023-10-29 at 1.23.03 AM
Screenshot 2023-10-29 at 1.23.03 AM2028Ă—170 27.7 KB

Screenshot 2023-10-29 at 1.23.26 AM
Screenshot 2023-10-29 at 1.23.26 AM556Ă—730 43.6 KB

Screenshot 2023-10-29 at 1.23.39 AM

Its not just in this activity.

All places where I create an audit trail, I find that the WU usage is very high

4

Moreover, I am just writing a text that “Image Uploaded” in the Audit Trail thing

5

How strange. I’d bet that the issue is with the Picture somehow - try removing all uses of the Pictures/Uploaders and see if that solves the issue. If yes, I’d say it’s a bug :man_shrugging:

6

Not only in the picture uploader, in other parts of my app too, where I create audit trail, the WU is very high

I am thinking of trying to replace the “Current User” object with the Name of user as text.

Also, I am thinking to use text instead of pulling texts from opticn sets

7

please don’t do this

please don’t do this also

Contact Bubble Support Center and see if they can explain why the WU usage is so high :confused:

8

ok
. Thanks for advice. I will send all my screenshots to bubble support.

9

Any other advice from anyone would be valuable. How can a click on button be so expensive.

10

@dr.sumit.periwal I am strongly reiterating what @georgecollier said: Please do not even consider this.

@georgecollier This prob won’t have significant impact on WU consumption (although who really knows) but what’s wrong with storing options as text (assuming they don’t have a whole bunch of attributes assigned to them?

11

ok. I have recently joined bubble to make an app. I am finding that the WU consumption for my one page app is very very high. With a single user and a single page SAAS, the WU consumption per day is around 3000 WU. At this rate, I can barely think to make my app economically sustainable on Bubble.

Is it me only or others are facing similar issue?

14

This is likely occurring because of one of the following
a) There are either major flaws in design / workflows;
b) Bubble WU consumption error; or
c) combination of a) and b).
Once the cause is resolved you will be able to make you app economically sustainable.

1 Like
15

If something’s a set of options, make it an option set rather than text (because that’s what they’re for). It’s just easier to manage in the long run. Same reason we often don’t store subscription statuses as text - sure you could, but why?

1 Like
16

There are a whole bunch of reasons, but the most common are for searching and sorting and *other values purposes.

1 Like
17

This topic was automatically closed after 70 days. New replies are no longer allowed.