Intermittent - 400 Bad Request errors

Windows Phone/.NET
1

Are you looking for help?

Yes, we’re facing 400 - Bad request error responses since about last 16 hours (or a little more than that) in our production apps.

These errors seemed to have gone away (resolved) after approx 2 hours of noticing it the first time. However we started getting the same after that. The error is inconsistent - half of the attempts will succeed while other half wouldn’t.

Note: Our production api and desktop app are published and distributed. There are no changes coinciding with the time frame when we (and other backendless users) started getting these errors.

Backendless Version (3.x / 5.x, Online / Managed / Pro )

Cannot get the the version number and plan info in the Backendless portal. Adding the screenshot below.
I am sharing app id, probably you can get to the information on your side.

Client SDK (REST / Android / Objective-C / Swift / JS )

.NET

Application ID

4E129FA8-ED2B-5021-FF84-966E95BC0D00

image
image1914×555 52.4 KB

Expected Behavior

Please describe the expected behavior of the issue, starting from the first action.

  1. API should work [consistently]. As it used to before the mentioned time.
  2. Secondary: The Backendless portal should work

Actual Behavior

1: The api doesn’t seem to work consistently, as mentioned above. Keep getting 400 - Bad Request error.
2. The Backendless portal should work as normal.

Reproducible Test Case

Calls to custom service fails intermittently.
Service name: admintoken
Method: validate

Please let me know if any other specific information is required to solve the issue. We’re facing this issue in production environment and all of our customers are affected.

Best regards,
Kinjal

1 Like
2

Hello @Kinjal_Desai

First of all, I apologize for the inconvenience. The problem has already been localized and is being resolved by our specialists. Is the app now working without errors?

Regards,
Inna

3

Hi @Inna_Shkolnaya

Thanks for working on it.

Yes it seems to be resolved now. I don’t get the error anymore.

What was the case this time? The issue lasted quite long this time compared to other times.

Thanks!

Best regards,
Kinjal

4

@Kinjal_Desai

It is related to an upgrade of the infrastructure we have to perform in order to support the growth of the platform.