Replica not removed if Offline Area removed while Offline

[DougBrowning]

I noticed we have a lot more Replicas now with Field Maps.  Initial testing shows that if I am online and remove a offline area the replica is removed.  But if I remove the offline area while the tablet is offline it does not remove the replica.  Even when I get back online and refresh the app, map, etc.  Testing with iPad Pro using AGOL hosted service.

Is there a trick to this?  Is this a known issue?

We have to move some content to a new owner and the admin is saying all replicas must be removed first.  I have 800 in just one service.  I think so many due to the above. Is this true?  Is there a API way to remove them all?

thanks

[Jeremy_Z]

This came up in a discussion today during a meeting with about 60 people in it, and many were discussing the same problem. Doug sent me this link and I thought I'd try to help bump it and see if there was anything new here. Maybe bringing @KoryKramer in to see if he had thoughts on it.

Users on the call were mentioning versions containing these replicas could only be properly deleted in ArcMap, but not in Pro. We just upgraded to ArcGIS Pro 3.1.3 and are going to be having very limited use of ArcMap at the end of February.

Is there a fix on the way for this, or is a new tool needed to allow removal of these versions in Pro? I'm not doing much versioning and such these days, but thought I'd try to help get this looked at again.

[ColinLawrence]

Hi @Jeremy_Z @DougBrowning ,

We still have an internal issue in where we have investigated this in the past and it remains open due to our inability to consistently reproduce the problem. For this reason unfortunately nothing has changed but we did realize we did not have a support bug to link to our internal issue, which will allow us to track the impact and different user cases where this may happen. Anyone on this thread should contact support and attach your account to the this bug: BUG-000153451

We will take another fresh look at this issue as well.

From the replica removal perspective, I do not believe anything has changed. You can remove them via a script or directly in REST. I am not familiar with using desktop to accomplish this workflow. 

[ODWC_GIS]

Hey there! Fancy seeing you again. 

I'm using ArcPro 3.2 and have just run headfirst into this issue. 

[DougBrowning]

Bump on this.  Been almost 4 years and we are still getting these all the time.  In Portal its even more brutal to remove all of these.  
Any updates?   @ColinLawrence   thanks a lot
https://support.esri.com/en-us/bug/the-replica-on-the-arcgis-rest-services-directory-is-no-bug-00015... 

[ColinLawrence]

@DougBrowning I havent been able to reproduce this problem in our upcoming Field Maps update on the new Maps SDK. I just double checked right now and still not running into it. Have you had an opportunity to test on the public beta for this Field Maps release? If not, could you give it a shot and see if you can reproduce the problem still? https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/arcgis-field-maps-beta-is-here

I dont want to rush into saying its fixed when im not sure if there is some wrinkle in your workflow that I am not accounting for. FYI we hope to be shipping this as a full release within the next few months.

[DougBrowning]

We are still seeing this all the time in AGOL.  Has become an extra workload.

This year we moved to Portal and there were are seeing replicas are never getting removed regardless of Field Maps offline or online status.  When I turn on Verbose logging and remove an offline area I see nothing at all happen in the log.  Like it does not even try.  It just keeps creating more and more Feature Service replicas every time I create an area.  Check in with some users and its widespread and they are adding up "50 users, 60 versions, and 1358 replicas".

@ColinLawrence Any idea what is up here?  We have thousands of users so this gets out of hand pretty quick.  Is something up in the new version?  

Thanks a lot

[ColinLawrence]

Hey @DougBrowning . I took a look on a 12.0 Portal, downloaded a few areas (both preplanned and on demand), and then removed them. I noticed one instance where our logging shows the unregister failed but I was simultaneously capturing the network traffic and that showed  `success=true`. I checked at REST and confirmed that replica had been removed as well. From then on whenever I restarted Field Maps, or change connectivity, it tries to unregister that same replica which shows a new failure in the logs and a failure in the network traffic as the replica with that ID does not exist. I am not sure if this scenario is contributing to what you are seeing or not but it seems like something we need to investigate regardless.

Just to note, you do not need verbose logging on to capture the [UNREGISTER] category in the logs. 

I am testing this more to see if I can get an actual failure resulting in an orphaned replica. I think it would help if you reach out to me directly via DM so we can coordinate via email. There are likely workflow/environment details that can help me reproduce what you are seeing. Thanks

[DougBrowning]

Great thanks for looking into it.  We got a ton of people out for the holiday so it may be next week before I get back to you with more.

We are at Portal 11.5.

I did have verbose on but will test again next week.  Thanks a lot!