Glitch project codes missing without any reason


#1


Basically I made this a month ago but then today the bot became offline and then when I checked it it, the code is gone? Is this a glitch error? The code was about 1000+ in lines
I didn’t edit the code since a week or so.


#3

Hey @Pokemonspecialist there does seem to be something odd going on here. I’d like to take a closer look tomorrow, but if you need the code back sooner than I’ll get to it (although even that will probably be tomorrow as well) I can give you a list of backups we have and you can let me know which one you want to restore too.

Sorry for the inconvenience!


#6

Ok thanks I’ll use a backup thanks


#8

Hey @Pokemonspecialist thanks for your patience - we were able to uncover what appears to be a bug based on your input.

Here’s a list of the backups we have for this project for about the last week or so:

  "0:2019-01-25T05:09:51.000Z",
  "1:2019-01-25T04:39:50.000Z",
  "2:2019-01-25T02:21:56.000Z",
  "3:2019-01-24T20:52:36.000Z",
  "4:2019-01-24T20:35:00.000Z",
  "5:2019-01-24T14:09:11.000Z",
  "6:2019-01-24T11:07:06.000Z",
  "7:2019-01-24T10:56:02.000Z",
  "8:2019-01-23T20:33:32.000Z",
  "9:2019-01-23T18:50:38.000Z",
  "10:2019-01-23T17:55:39.000Z",
  "11:2019-01-23T17:36:46.000Z",
  "12:2019-01-23T17:25:53.000Z",
  "13:2019-01-23T15:48:54.000Z",
  "14:2019-01-23T15:38:47.000Z",
  "15:2019-01-23T13:52:36.000Z",
  "16:2019-01-23T13:41:34.000Z",
  "17:2019-01-23T13:30:34.000Z",
  "18:2019-01-23T05:01:07.000Z",
  "19:2019-01-22T20:26:28.000Z",
  "20:2019-01-22T17:44:12.000Z",
  "21:2019-01-22T17:33:12.000Z",
  "22:2019-01-22T17:22:13.000Z",
  "23:2019-01-22T14:41:08.000Z",
  "24:2019-01-22T11:16:10.000Z",
  "25:2019-01-22T08:21:21.000Z",
  "26:2019-01-22T06:56:12.000Z",
  "27:2019-01-22T06:45:15.000Z",
  "28:2019-01-22T06:13:15.000Z",
  "29:2019-01-22T06:02:12.000Z",
  "30:2019-01-22T05:51:12.000Z",
  "31:2019-01-22T05:40:13.000Z",
  "32:2019-01-22T05:29:12.000Z",
  "33:2019-01-22T04:35:16.000Z",
  "34:2019-01-22T04:24:16.000Z",
  "35:2019-01-21T20:15:42.000Z",
  "36:2019-01-21T14:10:08.000Z",
  "37:2019-01-21T13:59:09.000Z",
  "38:2019-01-21T13:49:07.000Z",
  "39:2019-01-20T20:07:12.000Z",
  "40:2019-01-20T17:54:06.000Z",
  "41:2019-01-20T17:43:07.000Z",
  "42:2019-01-20T17:32:08.000Z",
  "43:2019-01-20T17:10:08.000Z",
  "44:2019-01-20T16:59:07.000Z",
  "45:2019-01-20T16:48:08.000Z",
  "46:2019-01-20T16:38:06.000Z",
  "47:2019-01-20T16:27:09.000Z",
  "48:2019-01-20T15:10:10.000Z",
  "49:2019-01-20T14:59:08.000Z",
  "50:2019-01-20T14:48:12.000Z",
  "51:2019-01-20T14:37:09.000Z",
  "52:2019-01-20T14:26:10.000Z",
  "53:2019-01-20T14:15:10.000Z",
  "54:2019-01-20T14:04:09.000Z",
  "55:2019-01-20T13:53:11.000Z",
  "56:2019-01-20T13:42:11.000Z",
  "57:2019-01-20T13:31:11.000Z",
  "58:2019-01-20T13:20:12.000Z",
  "59:2019-01-20T12:58:14.000Z",
  "60:2019-01-20T12:26:15.000Z",
  "61:2019-01-19T19:50:57.000Z",
  "62:2019-01-19T19:39:56.000Z",
  "63:2019-01-19T19:30:57.000Z",
  "64:2019-01-19T18:37:56.000Z",
  "65:2019-01-19T18:26:56.000Z",
  "66:2019-01-19T18:15:56.000Z",
  "67:2019-01-19T18:05:56.000Z",
  "68:2019-01-19T17:55:55.000Z",
  "69:2019-01-19T17:44:55.000Z",
  "70:2019-01-19T12:21:50.000Z",
  "71:2019-01-19T02:29:37.000Z",
  "72:2019-01-18T13:51:37.000Z",
  "73:2019-01-18T13:40:37.000Z",
  "74:2019-01-18T13:30:37.000Z",
  "75:2019-01-18T10:35:18.000Z",
  "76:2019-01-18T08:00:17.000Z",
  "77:2019-01-17T19:36:31.000Z"

Please let me know which one of these you’d like me to restore.


#10

“7:2019-01-24T10:56:02.000Z”
24th jan one


#11

Ok! I’ve restored that backup. Please take a look and let us know if that’s what you needed.

Sorry again for the inconvenience!


#12

I think the problem is from Glitch … Same thing happens to me .


#13

I hope this won’t happen again not with my main project


#14

Hey @Pokemonspecialist we’re pretty sure this was related to a momentary Amazon S3 failure yesterday, and we’ve deployed a fix to the bug that caused the S3 issue to result in rolled-back project state, so while there may be a few other projects that were affected and haven’t been restored yet, we don’t expect this particular problem to crop up again.

We’re very sorry for the inconvenience!