Recovery Mode failing to recover unsynced data after a "400: Unable to parse range" error

AppSheet AppSheet Q&A
1

Hi everyone,

I’m dealing with an issue where a couple of my apps suddenly disconnected from their backend table with the “400: Unable to parse range” error.

While I know how to fix the underlying connection issue, AppSheet’s Recovery Mode is failing to recover the unsynced offline data properly. Instead of cleanly pushing the data or generating a usable recovery file, the data is missing.

Has anyone else noticed a recent bug or degradation in AppSheet’s Recovery Mode when handling disconnected tables?

For those who have faced this, what is your most reliable workaround for extracting stuck user data when the native recovery tool falls short?

Thanks in advance for any insights!

image
image681×365 18.5 KB

2

Hi @Mholi

from AppSheet Help : Response HTTP status codes : Invoke an action - AppSheet Help

The API returns the following HTTP status codes.

200 Successes

400 Bad Requests

  • The Application Access Key is missing.
  • The AppId is missing.
  • The POST body contains invalid data.

403 Forbidden

  • The Web API is not enabled for this application.
  • The Application Access Key is invalid.

404 Not Found

  • The application specified by the AppId cannot be found.

500 Internal Server Error

3

IIRC, this happens if the worksheet named in the app’s table configuration doesn’t exist. Did you delete or rename the worksheet?