Hello,
I published items from ArcGIS Pro as web maps into ArcGIS Online. At first, it worked great, but then I wanted to make some changes and republish again. I did this a couple of times. Now I have all of these items in my AGOL Content that won't let me delete them. I get messages like "Cannot Delete" when I try to delete a Web Map or a hosted feature layer. Any suggestions would be greatly appreciated.
Thanks,
Derek
They may be delete protected.
Thanks for this suggestion, Laura. But, when I try to go into the item details, I get the message: The item you requested cannot be found. The item may have been deleted, or you may have entered an incorrect URL."
It probably was deleted then and the system hasn't caught up yet. I've had this happen to me before. Have you cleared your cache as well?
For the future you can try overwriting rather than republishing each time.
Yes it does feel like a system hasn't caught up sort of thing where items I have deleted are still showing up in my Content and Field Maps even. When you say Cache, do you mean my web browser or something ArcGIS-specfic?
Browser. I had a call to support for it and eventually it just went away. They would be your best bet if it doesn't resolve itself.
In addition to Laura's suggestion, make sure that there are no items that depend on what you are deleting.
@JohnDMorgan this recently happened to a content item on our site as well. The messages you describe were identical. I could not delete it manually in AGOL, nor via the ArcGIS python api, and the rest api wouldn't recognize it. The main difference from your experience is the item on our site was deleted, had been in the users recycle bin and then after 14 days it was supposed to be permanently deleted. It was instead returned to the users root content folder without anything but an object icon. I logged a ticket and support indicated it was a 'residual' item and the operations team needed to delete it from the back end of the system. For us this occurred on Wed evening (11/13/2024). That timing is correlated to the November update, however support did not indicate it was related.