Any Log Ninjas Out There?

We have an app that’s been completely built on Bubble. It allows businesses to get paid for live streaming their content to their clients and then archiving that content to sell again later.

In light of the current environment, we’re as popular as you think we’d be. We have 200 businesses a day enquiring about joining the platform. We have tens of thousands of users and are doing 300-700 page views an hour and we’re processing hundreds of thousands of dollars of payments.

That’s all great, but we’re finding that (i) the number one complaint BY FAR of businesses are that our platform is “glitchy” and “does something one time you click a button, but not the next when you click the exact same button in the exact same flow” (even though we’ve never exceeded 10% of our capacity on Bubble) which led us to find that (ii) when we check our logs for simple workflows related to the clients who are reporting these issues, we can’t search by user or keyword and when we finally do find them the events and workflows that have failed are completely missing from the logs.

Has anyone ever solved a similar problem? I’ve reported this issue to Bubble multiple times over a period of months through the traditional bug reporting flow, but haven’t gotten anywhere.

I know the Bubble team are working hard to keep bringing great functionality into the app, but they either don’t have time to fix this or it isn’t a priority so I’m looking for a workaround here. Has anyone found a way to access their system logs reliably without going through the Bubble logs page?

And beyond the logs themselves, has anyone ever experienced similar issues as you’ve scaled with your app? We’ve hit our market with the right product at the right time, but it’s been a super frustrating experience watching workflows we’ve seen complete a thousand times just fail randomly, cost us clients and then not even be able to see what happened so that we can try to fix it.

I find the logs extremely disappointing and have had very similar issues where once you hit thousands of users, the 1 in 1,000 edge case occurs but you can’t properly diagnose it because the logs are lacking and difficult to navigate.

I got around this in the early days by using FullStory to record user sessions, which you can then replay back. This can be amazing to help you troubleshoot very quickly, but you want to make sure your users consent to it before using it, as this would change the Privacy Policy you have in place.

This is super helpful @gf_wolfer - thank you. I’ve not had much luck getting traction on the log side, so this could end up being our only means of seeing how and why these errors occur.

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