If anyone has a minute, could someone help verify if this is a bug to report…
A quick note: It seems that at some point recently Bubble finally opened up backend workflows to the free plan. Thank you to the Bubble god(s)! This is such a positive step as there was no way previously to test a backend workflow on an app unless you started paying for an app plan immediately (the exception was of course Agency Plans).
Scenario: I was working on a new API call for a public workflow and I could not figure out why I kept getting a 401 unauthorized error in a brand new app (and yes I had all of the no-auth boxes checked - see below). This same API call was working with no problem in other apps.
After much testing of different scenarios I decided to try changing the app plan to the Agency Plan and the API call immediately started working.
To reproduce:
- Create a new app (on the free plan)
- Enable workflow and backend API
- Create a simple workflow, check all the boxes noted above to ignore auth, etc
- Use Postman to try to initialize the request (check if you get 401 Unauthorized)
If so, is this intended behavior? @georgecollier want to give it a go?
(and for what it is worth, I also tried using an API token to set the Bearer token and it still returned 401)
