Hey Kevin, we've identified the root cause of this issue and should have a fix out today or tomorrow. It's a bit complicated but I'll try to explain step by step:
1. The first time we tried to index those items our process failed
2. The second time we tried it succeeded
3. Bug: There was still a record of the failed document in the system
4. Bug: Our nightly reindexing process tried to reindex the failed document
5. Bug: The process above thought layers associated with the failed document were outdated and deleted them
We're going to fix these related bugs and make sure your items get back into the index.
To explain the other phenomena:
" Although in the search text which auto populates, the terms matching this item are presented."
- Autocomplete is still based on our older index. The switchover to the new index will be completed shortly. Autocomplete suggestions will then be in sync with documents that are on your site
"If I go and touch the item in arcgis.com (edit a field and push save)...it instantly becomes searchable in the hub site again."
- When you edit a public item, our system gets a notification to index the item. That indexing process makes your item visible. However it was still subject to the process overnight and would have been deleted within 24 hours.
"Even stranger - we have some hard coded links to the pools item, and they return a hub 404 error when clicked."
The same index that powers search also serves content. So if something is not visible in search (with the exception of autocomplete described above), it won't be linkable either.
I'm sorry you hit these bugs, but I am very thankful you brought it to our attention. This was a particularly tricky and insidious one so I am grateful to have caught it during the beta period.
Thank you,
Daniel Fenton
Search Engineering Lead | ArcGIS Hub
.png "DanielFenton1"){kind=avatar}
