Logging, Transitions, and Regenerate

When you are accessing replicas on the Operational Maps tab of the Mapping plugin, several handy ways to curate and act upon targeted data are available to you.

View Logs

On the Operational Maps tab, click a map in the list on the left, then on the right click Replicas. When you click a replica, you have the ability to access a myriad of information about your replicas and deltas. The View Logs button links to the Logging tab, and upon clicking the button, a query is executed that provides all logs for your sync service. This is specifically beneficial in those instances when you see a replica or delta taking an inordinate amount of time to finish, or if an error was encountered.

TIP: Logs go back 90 days, so if you have an item that was created more than 90 days ago, the View Logs button is disabled.

This tab provides a full list of logs, in addition to ways of filtering the copious amount of technical information provided. On this tab you can view specific issues according to:

Timeframe (#1 in the image above)
Minimum level of issue (#2)
Advanced filter (#3)
Available filters (e.g., Exclude service bus errors, #4)

Once you’ve applied one or more filters, click the Run button on the left. You can also perform a search using the Search field at the top of the app.

If you are viewing replica details, View Logs shows you the logs for all of the deltas.

Transitions

Transitions are intended to be a visual representation of where the replica or delta is regarding its creation.

Submission – the request to create the replica or delta was successfully sent to the integration service.

TIP: If it appears as though the creation request seems to be taking too long, a likely culprit is that the ArcGIS server hasn’t received the request. Therefore, the integration service might not be picking up the message and sending it along to the ArcGIS server.

Start – the ArcGIS server has successfully begun creating the replica or delta. The submission resides in this state the longest. Once it moves to this state, it either finishes or issues an error.

End – the replica or delta has been created, or an error was encountered.

If a replica or delta gets submitted and proceeds to the Start state, it is unlikely that it will appear to be stuck. If the replica or delta doesn’t make it to Start, then something significant is wrong.

Regenerate

Consider this handy functionality in the event you notice, for example, that a replica seems to be spinning indefinitely upon creation.

Rather than completely recreate a replica if there’s an issue, this button does all the manual work. This is useful for two example reasons:

The replica transitioned all the way to the end but produced an error. Rather than going through the motions of creating a whole new one, this feature performs all of it for you. Once that is successful, the old information is automatically removed.
Users in the field are interacting with replicas within tile packages, and you need to make an edit (e.g., add a layer, add a field, remove a field, etc.), which Esri considers a schema change. For offline data to continue working as expected and be in sync with online data, the replica needs recreated for all regions, and all the old information needs deleted. This button recreates everything for you plus any schema changes you made. Once that is successful, the old information is removed.

If an offline package is large, your users might get a prompt to redownload, but the process is otherwise invisible to them if they already have the offline package downloaded. However, if users have made a fundamental change to the operational map, the online data won’t update until they restart the app. If you regenerate replicas for any reason, then ask your users to restart the app.

IMPORTANT: Logging and Transitions are only available if you have hosted sync.