Because of the way Algolia is designed, performing a restoreApiKey may not
succeed because the previous deleteApiKey takes some time to get propagated
to all Algolia servers, giving us the following response: [404] Key already exists.
To prevent that, we need to change the testApiKeys CTS test, if implemented,
to retry even on [404] Key already exists response.
Because of the way Algolia is designed, performing a
restoreApiKeymay not succeed because the previousdeleteApiKeytakes some time to get propagated to all Algolia servers, giving us the following response:[404] Key already exists.To prevent that, we need to change the
testApiKeysCTS test, if implemented, to retry even on[404] Key already existsresponse.