Setting up Stripe syncing with Bubble database today and learned for the first time that trigger names can conflict with backend endpoint names. That is to say, if you have a trigger named invoice and a backend workflow named invoice, Bubble will return a workflow not found error when you try to call that endpoint. The trigger will still work. I’d always assumed the name of triggers wouldn’t conflict with endpoints but today shows I was wrong so putting this here for anyone that may bang their head against the wall trying to debug something like this later ![]()
Interesting thanks for sharing!
It might be because Bubble puts API workflow, DB Trigger, Recurring Event under the same Backend workflow umbrella.