Export data blocked

General
1

I’ll explain my problem by indicating the chain of events:

  1. Having exceeded the plan limits I tried to export all the data before deleting it.
  2. Then the dashboard warns you that export is not enabled while having exceeded the plans.
  3. I delete some rows from the table that was exceeding the limits and try to export again.
  4. Now a warning tells me that I can not export since an exporting operation is still unfinished.
    A notification email will be sent, but it never arrives because is not really going on any operation…
    You can see the image attached for further references.

prov.PNG
prov.PNG2559×196 43.6 KB

2

Hello,

What is your application id? I will unblock your export.
Also, I have created internal ticket BKNDLSS-16807 to fix it in general

3

The app ID is FAAC6BED-DDD1-AFF4-FF65-D5717185BD00

Now the rows are exceeding again the limit because I couldn’t find a place to pause the APP like in Backendless 3.X there was.

Last time the exceed was 200 rows, so I deleted it manually to come under the limits using the Console. But now the exceed is 4678 rows…

I find annoying that the export feature is disabled just because the limits are exceeded, there’s no way to save the data because you have to delete in order to export.

How can I delete 5000 rows and export before my users override the limit because I can’t pause the app?

4

Ok, Thanks Sergey,

BTW, I am trying queries in the Console using the SQL Search tickbox so I can make a SELECT based on “created” to get all the last 5000 rows. But once I have them in the console, how can I delete all of them at once? If I click in delete, it only deletes the 15-30-50 rows displayed in that moment in the actual “page”.

5

You can delete it from REST console using bulk operation

6

You can remove it with bulk delete https://backendless.com/docs/rest/doc.html#data_deleting_data_objects

now you should be able to export data after you decrease number of objects

7

I have decreased the number to 299924 objects, below 300,000 (my limit) and when trying to export same warning again: One migration in process, bla bla bla…

I have lost another 5000 objects…

8

So after deleting another 4000 objects I’ve been able to export the data, better said, I have received a message that my data is being exported.

In first place the link in the email that the server sends is broken, this is a screenshot of the email, as you can see the download link is not “clickable” because there’s no URL to download, just the name of the file and the internal address in the files directory. (I warned about these some months ago…)

http://support.backendless.com/public/attachments/c787ef8f3d9762dfcb1661d117add45d.PNG</img>
Because I’m aware of this, my procedure is to go to “Files” and then “export” and then download the file from the console, but this time a new surprise was awaiting when opening the Files section:

http://support.backendless.com/public/attachments/2cd53facaced27d5eb4b1f85c5e7c0f6.PNG</img>

So, long story short, I still can not export the data, therefore I can not delete the full table so the limits will be overridden soon again, so I will have to delete more rows that cannot be exported because the service is broken.

It’s incredibly frustrating to use this service honestly. We pay for having a “server” and not to have to worry about one, but every time that I try to do a new thing, I have to create new tickets because something fails.

c787ef8f3d9762dfcb1661d117add45d.PNG

2cd53facaced27d5eb4b1f85c5e7c0f6.PNG
2cd53facaced27d5eb4b1f85c5e7c0f6.PNG2048×488 34.1 KB

9

For your convenience, I tell you that that problem doesn’t happen in other apps so probably is related to the unblocking for exporting that you applied yesterday. THIS NEED TO BE SOLVED please.

Finally, I have downloaded the file using the REST API so I don’t longer need help with the exporting issue.

10

Hi Jose,

We’re already working on a fix for the File Service. While it’s inaccessible, we can send you the exported archives manually if you need.

11

The issue has been fixed. Sorry for the inconvenience.

12

I exported them using Rest API Sergey.

Do you know if the blocking when trying to export them can be produced again if I hit the limits, try to export, correct the usage under the limits and then try to export again, as my original question up here in this thread?

13

I managed to reproduce the error by the steps you described and created an internal task BKNDLSS-16845 to fix this.
Note that the export block is automatically released after 1 hour, so for now you will be able to export the data an hour after you correct the usage.

14

Ok, ,I’ll take that into account if it happens again. Thank you.

15

Jose Luis Martín,

We’ve released a fix. Should be fine now

Anton