Cloning to AuraDS from AuraDB fails

Update timeline

1. investigating May 30, 2024, 11:07 PM UTC

   We are currently investigating an issue where customers doing a clone operation from AuraDB to AuraDS will see a failure. We will keep you updated as we determine the cause of the issue and work toward a resolution.

2. investigating May 31, 2024, 04:05 AM UTC

   We are currently investigating an issue where customers doing a clone operation from AuraDB to AuraDS will see a failure. We will keep you updated as we determine the cause of the issue and work toward a resolution.

3. investigating May 31, 2024, 07:02 AM UTC

   We are currently investigating an issue where customers doing a clone operation from AuraDB to AuraDS will see a failure. We will keep you updated as we determine the cause of the issue and work toward a resolution.

4. identified May 31, 2024, 11:39 AM UTC

   We have identified the root cause and can confirm that only cloning to AuraDS is impacted. A small subset of customers using AuraDS may be affected. We are working on a fix.

5. identified May 31, 2024, 09:15 PM UTC

   We have further narrowed down the root cause and can confirm that cloning from some existing AuraDB instances to other AuraDB or AuraDS instances is impacted. A small subset of customers using AuraDB may be affected. This effects ONLY existing AuraDB instances that are running version 5.20. To determine if you are impacted, use cypher to check your Neo4j version (see example). - call dbms.components() yield name, versions, edition unwind versions as version return name, version, edition; - Neo4j Kernel 5.20-aura enterprise We are working on a fix, which is to roll out 5.20. We will update this incident with an updated status on Monday, June 3rd.

6. resolved Jun 04, 2024, 09:57 AM UTC

   We have now completed the roll out of the 5.20 versions to all tiers of Aura and this now address the issues with cloning.