Yesterday and today, also again just now, I tried a couple of times and the report won’t delete, so it feels like the issue is persistant. These attempts were manually through the Kobo website interface.
A curl request to the API v1 to delete the report through a script gave a server response back as if the delete was successful, but in reality the report is still present. Since the API v1 doesn’t give an error back, people who have automated their report handling are not notified that something went wrong. This can cause problems in data sets.
Would be great if it would be fixed, many thanks in advance!
Hi @bert12, I apologize for missing this response. It looks like the same issue from here. Can you and @mandarsathe please send me a private message with the following:
Bjr, j’ai besoin aussi de l’aide à ce sujet, j’ai le même problème que sur 2 enregistrements, les autres je parviens à supprimer mais pas 2. Que faut-il faire?
Merci
Bjr Kal, Merci pour la réponse, je veux savoir comment envoyer le message en privé ou bien je dois juste réponse à votre message, comme je suis entrain de le faire maintenant. Merci de m’indiquer le chemin à suivre.
Hello, I’m Andy and experiencing the same issue, but from the API (started on Friday I believe) where I can’t delete entries. We’re connecting to https://kc.humanitarianresponse.info/api/v1 and the login is xxxxxxx. The specific survey that failed was 476370, though there may be others. The first entry to fail was 221028360. Thank you for your help in getting this back up as it is a mission critical part of our system!
Andy
Merci beaucoup, mais j’ai un message d’erreur à l’envoi du message personnel, le voici:
“Désolé, vous ne pouvez pas envoyer de message personnel à cet utilisateur.”
I am a bit gunshy about and manual deletes since our script only deletes after verifying a successful copy. It has worked perfectly for over a year until a few days ago (similar to the other posts on the forum). Thank you,
Andy
Hello, just reopening this issue as we’ve been getting the same error again on our delete requests. It was fixed for a day or so and then reverted to bring broken. What is going on in the system? Is it something you can patch again? Thanks,
Andy