Deleting responses abyssmaly slow | XM Community
Skip to main content
For the past few weeks, whenever I go to clean my data set and delete bad responses, Qualtrics has taken a reallllly long time to process the request. Is there something going on behind the scenes that has caused this sudden slow down?
I'm not a behind the scenes person... but agreed it has taken 10s of minutes for things to delete. Any sort of manipulation on that page that does not involve a download has been taking forever
I had trouble for awhile with specific surveys not seeming to index or process requests. I was able to reach directly out to support as it became problematic and they were able to do a manual indexing that made things go much faster. My primary problem was with indexing however and not deleting, but it may still be worth you reaching out directly to Support.
Thanks! I had have issues with indexing before too and reached out to them regarding that. It would happen whenever I would edit data in the "Data and Analysis" screen. The page would try to refresh, but there would often be responses caught in some weird kind of limbo - unable to get updated. They taught me a work around setting embedded data that would correct the issue. It seems like these are two significant flaws to the technology that need addressing. So long as they are present, all the fancy data manipulation tools are not much good to a user.
I too have been experiencing this. I have found that refreshing my internet browser after waiting a minute or so tends to delete the data much more efficiently.
I know this is a few months late, but my coworkers and I have been experiencing this issue as well. I contacted support the other day when the slowness evolved into issues fully deleting and importing datasets despite saying the requests were complete.



Support gave me a solution which allowed me to solve this problem the next time it arose. Add a new embedded data variable in the Survey Flow. This forces the dataset to re-index. This seems to resolve any lingering requests which seem to be complete but actually aren't. You can remove the embedded data afterward.



I hope this solution helps others!
We had a similar issue (with a response missing in the list) and discrepancy in the response totals. As suggested above and demonstrated by @Ketonjo in a similar situation, we also added embedded data to the survey flow. After re-indexing, the missing response appeared and the discrepancy resolved. We also removed the temporary element in the survey flow afterwards. Thanks for everyone's comments. Helped a great deal.

I am also having this issue. Would appreciate a step-by-step walk through of how to add embedded data to the workflow to fix this issue if someone is willing. Or if someone from Qualtrics can just fix this problem that would be great!


brad7280
The steps are:

  1. Open the survey, navigate to the Survey Flow

  2. Add new element

  3. Select "Embedded Data"

  4. Select "Survey Metadata" in drop-down menu

  5. Select "Embedded Data" in list

  6. Select "Apply"; SAVES your survey flow changes

  7. Access survey responses via Data & Analysis

It should re-index your responses and correct the issue. I don't believe you have to publish to make it work, but if you don't see any changes, try publishing and see if that makes a difference.
I have created a very brief video showing the steps. Hope this helps. https://drive.google.com/file/d/1sVaIRf72MlooGnzpGx4o3Nubg-3-I_FS/view?usp=sharing


Chanda_IUK thank you so much for this comprehensive explanation. I have followed these instructions and, even after clicking "publish," the problem remains, unfortunately.
Screenshot 2021-11-08 165336.png


I recommend clearing your cache and cookies, then try again. To note, sometimes it doesn't change immediately. Perhaps after you clear your history, you wait a little bit and then see if it is resolved. There are times that I don't see an immediate response to a change.


I just spent about an hour on chat working with them on this issue and they ultimately said:

 

Agent: Ok! So it seems our servers having not as strong as usually and this is why we are unable to delete it right now. This situation should be fixed by the afternoon so I'd recommend waiting and trying again then. :)

   

Me: The same thing has been happening since last week, I only contacted you today as a last resort, I don't belive it's an isolated incident.

  

Agent: I understand. Due to a high volume and demand going on in this specific server, some tasks require more time than intended

   

I truly apologize for the inconvenience

  

Me: So the solution is for me to just keep trying and hope that at some point I hit a window where there isn't high demand on the server?

   

Agent: Our engineering team is trying to solve the issues related to this so the capability of our server is at our clients level

   

I then again apologize for this, Phillip

   

Me: Wow. Alrighty then, that's pretty weak CS.

  


Leave a Reply