Support Topics Documentation Slack YouTube Blog

Error Message for Service


Update - This has started working again today, so it must have been something at your end…I guess?! Where this threw me, is the error message mentioned ‘sandbox’ and I as far as I understood it, I am not working in a sandbox. Anyway, all OK now.

Can someone help with the below error message?

I had previously created an API services to pull 100+ records into Appgyver and tonight it has stopped working. Thing is, I was experimenting with the API GET COLLECTION configuration within Appgyver but I reverted everything, and now I am getting this (what I was trying to do was configure a URL Placeholder, so I had altered the URL slightly but it is now back as it was…) What is stumping me is why the Service is not working with the Table within Backendless…how me fiddling with Appgyver has broken the service within Backendless.

Any help appreciated?!


Are you looking for help?

This is a support forum for reporting issues related to Backendless services. Please note that due to our support policy we cannot provide you help with debugging your code, consulting in regards to any language or third-party library usage. For this kind of questions we recommend using more appropriate forums like Stack Overflow.

In order to suggest you a quality solution, we shall usually ask you to provide the details mentioned below first. Including them into your topic right away helps us to start investigating your issue much faster.

In case you have a suggestion or an idea, the details below are not always required, though still any additional background is welcome.

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

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

Application ID

Expected Behavior

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

Actual Behavior

Please provide a description of what actually happens, working from the same starting point.

Be descriptive: “it doesn’t work” does not describe what the behavior actually is – instead, say “the request returns a 400 error with message XXX”. Copy and paste your logs, and include any URLs.

Reproducible Test Case

Please provide a simple code that could be run in a new clean app and reproduce the issue.

If the issue is more complex or requires configuration, please provide a link to a project on Github that reproduces the issue.

Hello @Paul_McCullen

Please provide your applicationId.

Is this error still reproducible for you?

Hi Vladimir

Sorry, my post is unclear as I updated it today, after initially raising the issue yesterday…but it starting working correctly today, so I cannot reproduce it… It was really odd as I hadn’t done anything in Backendless BUT I was messing around with the API in Appgyver that calls Backendless.

Today, I have added four new tables to Backendless and configured what I was trying to do yesterday in Appgyver…which was a ‘URL Placeholder’ and the URL is now referencing each table as required…so definitely working great today.

My app id is DE9727E5-8683-E098-FF56-9D23955C8300