Select to view content in your preferred language

Survey publishing hangs on "Updating survey form package"

2048
23
02-08-2024 01:57 PM
FOMELC01
Occasional Contributor

I have two surveys which hang regularly when I republish them. They seem to be OK when I update them on my phone, but I have to be concerned that there may be some unseen problem that will affect data collection. I don't want to give the survey out to my volunteers if there will be a problem with the data. I have not renamed the survey files or made any major changes. One survey is just a new version of an older survey with a couple new modules added, but I'm not trying to add those modules to the old survey. I'm creating an all new survey with those new modules.

Both surveys seem to consistently hang on republishing. 

0 Kudos
23 Replies
abureaux
MVP Frequent Contributor

Is this AGO or Enterprise?

How many repeats does the survey have (If we are talking <15, probably not a big deal)?

And have you used the built-in "Analyze Survey" feature in Connect (this wouldn't help with things like database integrity, but can at least tell you if you are doing something really wrong in the XLSX - which may in turn be causing a performance issue)?

0 Kudos
FOMELC01
Occasional Contributor

This is in AGO. The survey with repeats has only two repeats. I did run Analyze Survey and there were no issues of importance. After posting the earlier post, I deleted both surveys through the Survey123 website, made sure the surveys were gone in AGO, and removed (renamed) the .iteminfo file. I didn't move anything from the folders they were in. I then even rebooted my machine and tried to publish one of the surveys again, probably about an hour ago. Connect is again hung, now at "Creating form item". 

The survey shows up on the Survey123 website again. I deleted it from my phone, then reinstalled it from the QR code on the website and it appears to be as it should be. Connect is still running on the same survey, hung at "Creating form item". 

0 Kudos
DougBrowning
MVP Esteemed Contributor

Big media folder at all?

FOMELC01
Occasional Contributor

One 116mg tpk file. It doesn't seem larger than others I've had.

abureaux
MVP Frequent Contributor

Generally speaking, sounds like everything should be working.

How is you internet speed/stability? I have seen that in the past with people on less than ideal internet.

I have also seen those same people somehow get Portal "stuck" on a specific survey name, and the only solution was for me (more reliable internet) to publish for them under a new name.

If you create a new survey (stick with Connect's default name of "Form X") and publish, do you see similar behaviour?

If not, can you copy-paste the contents of your problematic survey into that XLSX (be sure to paste as TEXT ONLY) and republish, do you see similar behaviour?

0 Kudos
DougBrowning
MVP Esteemed Contributor

Did you maybe move anything in AGOL from the folders they were in?  You cannot rename or move anything.

abureaux
MVP Frequent Contributor

Would that cause it to hang, or just fail outright? It sounds like they are eventually publishing, but just taking longer than normal to do so.

(Agreed though. Never rename or move any of the files that S123 creates for you)

abureaux
MVP Frequent Contributor

I decided to try this out. Renaming the files/folder created by Connect doesn't seem to affect the publishing or data collection (at least for a very small test survey - I still wouldn't recommend trying this). But moving the files created by Connect to a different folder does cause a republishing hang from which Connect wont recover.

abureaux_0-1707431759127.png

Again, not sure if this is the scenario described here since it sounds like Connect does eventually publish. If that is in fact the case, I am inclined to think that the survey itself may be too large/complex.

0 Kudos
FOMELC01
Occasional Contributor

I haven't done any moving or renaming of files (other than renaming the .iteminfo file) either on my local machine or in AGO. My last publishing attempt (described earlier) was as clean as I could make it without starting a new survey from the XLSX form.

0 Kudos