Intermittent Issue with API Calls in Bubble

Need help APIs
1

Hi everyone,

I’m experiencing an intermittent issue with API calls in Bubble. Some requests work perfectly, while others simply don’t trigger or fail, without a clear pattern.

Context

  • My Bubble app makes API calls to Xano via the API Connector.
  • The same request works correctly in Postman and in other external environments.
  • In the test environment (test), some calls work, but others fail.
  • In the live environment, most API calls fail, and they don’t even appear in the Network tab of DevTools.
  • I have removed and reconfigured the API in the API Connector, but the issue persists.
  • Bubble’s Debug Mode shows that the workflow stops at the API request step, without any visible errors.

What has already been tested?

:white_check_mark: API Connector is correctly configured (and works for some calls).
:white_check_mark: Authentication credentials and tokens are correct.
:white_check_mark: The API works in Postman and other external environments.
:white_check_mark: No request limits or restrictions on Xano.
:white_check_mark: No visible errors in the DevTools console.
:white_check_mark: Tried creating a new workflow with the same API call, but the issue persists.
:white_check_mark: Tried removing and recreating the API Connector setup.
:white_check_mark: No differences between the Test and Live environments (the workflow is identical).

Error Behavior

:red_circle: Some calls appear in the DevTools Network tab, but without a required parameter.
:green_circle: Other calls in the Test environment work correctly, with the correct parameter.
:red_circle: In Live, only the incomplete requests appear in DevTools; the correct ones never trigger.
:red_circle: Some requests that don’t require parameters also fail, so it doesn’t seem to be a data issue.
:red_circle: Bubble stops executing the workflow at the API request step, without showing any visible errors in Debug Mode.

Possible Causes Considered

  • Internal Bubble rate limits?
  • Some instability in Bubble itself? (I checked status.bubble.io, but there are no reported issues).
  • Some internal Bubble setting preventing certain workflows from executing?

Has anyone faced a similar issue or has any ideas on what might be happening? Any insights would be greatly appreciated! :folded_hands:

2

There’s no rate limit for making API call from API Connector. Only API provider could have rate limit.

Some user reports some issue with API connector today, so this could be a Bubble bugs. Fill a bug report.

The last thing I can suggest is to make the same call from postman and Bubble (in run mode and API connector if you want) to a service like requestbin and compare both request (including headers). Be sure there’s nothing missing.

3

Thanks for the reply, friend!

I’m aware of the rate limit, but I didn’t want to dismiss it. Which leads me to believe that it’s a Bubble bug, but I haven’t received a response from them.

I’ve already redone the API requests, compared them and everything. There are no errors in them.

I don’t know what else I can do, I’m losing money with this.

4

@fede.bubble Can you ask team if there’s something wrong with API request? There’s a lot of users complaining since yesterday about sudden issue with API connector…

2 Likes
5

Asking the team if we have spotted anything broken on our end.

I’m assuming users have been submitting bug reports for this?

6

From what I read here, yes.

7

I have sent reports about this (#247749) but have not received a response yet, unfortunately.

8

We found the issue!

I came across this video (https://youtu.be/IGbDmciBwKs?si=Ct9KMYIhE20t_iGS) that explains how Bubble struggles to process empty arrays when it expects this type of data, but the response from Xano doesn’t include them.

We ran a test by removing these fields from the response—specifically the date lists—and it worked!

It’s likely that Bubble underwent an update that caused this issue, as everything was working fine before.