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!
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:
- Open the survey, navigate to the Survey Flow
- Add new element
- Select "Embedded Data"
- Select "Survey Metadata" in drop-down menu
- Select "Embedded Data" in list
- Select "Apply"; SAVES your survey flow changes
- 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.
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
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.