"Fail to Save" Error when attempting to change Share Results settings

[RMill]

I'm running into a "Failed to save." error when trying to change the share results under the Collarborate settings for a survey. The survey was create in Survey 123 Connect, was published with no errors, and the media folder is less than 10MB (saw this as an issue in another post). I need to change the setting so that field techs can create reports.  Currently others can collect, and a few surveys have already been submitted so republishing the survey isn't ideal. I know this has been an issue in the past. I tried EricaNova's solution on this post, but it did not work for me. 

I've tried changing other settings on the Share Survey page and they were able to save. However, when I change the collaboration setting and hit save I get a Failed to Save pop-up.

What the details say are in the attached text file.

I'm completely at a loss on what to try next. Any tips or ideas would be greatly appreciated.

Thanks

[abureaux]

Are you the owner of this survey? Is this the only one having this issue? And have you tried changing permissions directly from the Portal?

The error you seem to be getting is that it "already exists".

[RMill]

I am the owner and so far this is the only survey I have published that I've had others use. The field techs can use and submit surveys but they cannot view the survey on the Survey123 website in order to create the reports. 

By portal I assume you mean the AGOL account... everything in AGOL related to the survey is shared to the organization

[abureaux]

Right. Portal/AGO.

Did you (or anyone else) move these files in AGO? When a survey is published by S123 Connect or the S123 Web App, they need to be kept in those default file locations. If you go to AGO, you can search for the folder and check that the files are all there.

If files haven't been moved, you can try this from ZhifangWang (source) :

Like Johnathan Hasthorpe‌ suggested, it's always a good practice to clear the browser cache after each release of the website.

When sharing the survey to other stakeholders, following things will happen behind the scenes:

1. If not exists, a feature service view item will be created with the name pattern: {survey name}_stakeholder

2. The new created stakeholder feature service view item will be shared to the sharing level you specified in the Analyze tab of Collaborate page

3. The form item will be shared to the sharing level you specified in addition to previous sharing level. For example, if you want to share the survey to the stakeholders in group A and B:

  * If the survey has never been shared before (including in the Submit tab), then after sharing, the form item and the stakeholder feature service view item will be both shared to group A and group B

  * If the survey has been shared before, such as the form item is already shared to the org level and also group C (as fieldworker role), then after sharing, the form item will be shared to the org level, group A, B and C, the stakeholder feature service view item will be shared to group A and B

To fix the issue manually, please go to the My Content page of ArcGIS Online and open the survey folder, then following the exact steps below:

1. Delete the stakeholder feature service view item with the name pattern: {survey name}_stakeholder

  * Do not delete other feature service item that may contain your real survey data

2. Unshare all remained items in the survey folder

3. In the Survey123 website, go back to My Surveys page, refresh the page

4. Go the Collaborate page, and share it to other stakeholders you want

Note: you may need to fix the sharing relationship as fieldworker role by sharing the survey in the Submit tab of Collaborate page again

In addition, can you please answer the following questions to help us try to find the reason of the bug?

* Is the survey created in Survey123 Connect or Survey123 website?

* Is the survey created in very early time (which is "code sample" item type in ArcGIS Online) or a recent time (which is "form" item type in ArcGIS Online)?

[RMill]

The files have not been moved. I tried this previously and it still did not work. 
I ended up just publishing it as a new survey.

[abureaux]

Frustrating!

That was going to be my next suggestion. At this point, I'd simply recommend watching the layer/environment to see if anything happens which may result in this reoccurring. Though, hope is this was a one-off event that doesn't reoccur.