Request for Support

[Rob_Hughes_32Alpha]

Every month I update an Insights service for a client with a feature service. Each time we update the feature service we double and triple check the schema is the same, but when we click "refresh" on the data in insights, it breaks. No error message given besides "Something went wrong" - very helpful thanks.

On having to rebuild each of my 26 dashboards all have to have the custom symbology put back on and it takes hours when this should take minutes. Please can somebody from the Team get in touch with me directly.

[Ian_Muehlenhaus]

Dear @Rob_Hughes_32Alpha,

I'm sorry to hear about this issue. I do not have an immediate answer, but I've forwarded your question along to the Dev Team. Hopefully we will get some trouble-shooting advice soon regarding this situation. 

Thank you for using Esri Community to post your question and look for feedback. Again, I'm very sorry for this inconvenience, and I'm hopeful someone more expert than myself will be able to help you find a solution to this issue.

Sincerely,

Ian 

P.S. The SWW (Something Went Wrong) error typically means something is going amiss outside of Insights or in communications between Insights and a data repository (i.e.,. a specific error is not identifiable by Insights, because it is not specifically occurring within the Insights software).

I empathize with you, as the enigmatic nature of the SWW message can definitely be frustrating. 

[Ian_Muehlenhaus]

Quick follow-up question, @Rob_Hughes_32Alpha:

Do you know if you (or the client) are using ArcGIS Online or Enterprise? This will help.

Thanks!

Ian 

[Rob_Hughes_32Alpha]

Hi Ian,

We are on ArcGIS Online. We just checked again that the schema is the same, shared to the same groups and sitting in the same area. We also re-shared the service and this time four out of the 26 dashboards updated fine and the rest broke again. It feels like an AGOL issue, I would be keen to talk to someone from tech support if possible.

Cheers,

[Ian_Muehlenhaus]

One quick thought is that it may take up to an hour for refreshed feature services to appear:

https://support.esri.com/en-us/knowledge-base/faq-why-is-my-hosted-feature-layer-view-not-updated-in...

However, this doesn't necessarily explain the SWW error. 

A second member of the dev team posited the idea that "Update"-ing the datasets in Model View may work better than refreshing them. This may be worth a try.

Finally, we did fix a bug pertaining to this type of issue in the 2023.1 release.

However, there is a chance it was fixed on our end and not on the AGOL end. I'm still following up on this lead. 

Final follow-up question for today:

Are you only working in AGOL or are you working in Desktop to AGOL?

Sorry again to hear about this issue.

Best,

Ian

[Rob_Hughes_32Alpha]

Ian,

The refreshed feature services not appearing point - it appears in "add data" and I have to add it, switch it out in model view and then resymbolise the map (actually that point relates to a feature suggestion I put in a while back - having style configurations as part of the model).

Unfortunately I've tried in the data pane on the side, an overall refresh on the bottom and refreshing in model view. What's annoying is that once it fails there is no way to revert and there is no button to update either, so I have to refresh my browser and potentially go back a few steps if I forgot to save.

Interesting about the the fix - would be good to find out more about that and when it will be deployed wider.

I am working in AGOL. I'd like to work in desktop but since the workbook exists in AGOL already and I need to work across two computers I have to use the cloud version (another feature suggestion I put in was working across desktop and AGOL you might remember).

In an ideal world I'd like to be able to refresh the whole workbook and share all pages at once too, with confidence that the data will update as expected with no errors. Keen to help the devs get to that if I can at all.

[Ian_Muehlenhaus]

Hi Rob,

I remember your idea posts. They were great! And we truly appreciate these types of feedback. 

I will keep you updated on any other updates I hear from the dev team. Group consensus right now is that this is likely an issue on the Feature Service/AGO side, but we'll see. And that doesn't mean we can't help troubleshoot the problem further.