[SOLVED] 2019-09-19 Schema and Content is Gone

Maintenance
2

Are you talking about self hosting or cloud? Have you recently updated the version, e.g. to dev?

Where are you hosting?

3

Hi Sebastian,

We are using cloud, and the content is hosted under Squidex. We havent updated anything (Last update was August 22)

4

Okay, it seems that some indices are corrupt. I will recreate them and see if it solves the issue. Will get back to you in a few minutes.

5

Thank you Sebastian! We will wait for your update.

6

Indexes look okay now, but it does not seem to solve the issue. I will debug it locally and update you asap.

7

Thanks Sebastian! We appreciate the assistance

8

Hi

I’ve got exactly the same problem. Posting to follow this issue!

Kind regards
Lode Kennes

9

I have found and solved a bug in the indexer. I have fixed it and it is in the CI pipeline now. I will deploy it asap and keep you updated. Sorry for the inconvenience.

1 Like
10

I think the error is fixed. Can you please have a look to your schemas and verify it? I will write a postmortem after that.

11

Hi Sebastian, I can confirm that this fixed the missing info. Thank you for the assistance!

12

Also to add, is there a way that we can download a backup of the schema, etc so in case this happens at least we have a backup that we can use?

13

You can use the backup system for that, but the schema was never gone, it was an indexing problem. I will explain the reasons in the post mortem.

14

See: 2019-09-19 Schema and Content is Gone: Post Mortem

15

We are still experiencing this issue, the schemes are fine, but all the content are gone

16

content pages return either 429 or 404 errors

17

Can you give me an example request and app name + schema name?

18

Do you get the error only from the API or also the UI?

19

Both, the request is https://cloud.squidex.io/api/content/reuring/content-footer?q={"take"%3A10%2C"sort"%3A[]%2C"filter"%3A{"and"%3A[]}}

edited: sorry I can only reply max 3 messages per thread. Thanks the problem is solved!

20

Do you remember if you have every recreated this schema?

21

429 usually means that you have exceeded your API calls. I see that you have used 165k of 150k. I will reset the usage for your for this month.