View source for GR:Gravity/Xref/Locations/Location Status

=== Location Status ===
As can be seen in the image above a location also has a status field that is represented by an icon. The status is 1 of 4 values:

* [[Image:xref_loc_status_scheduled.png]] scheduled, waiting to be indexed.
* [[Image:xref_loc_status_loading.png]] loading, indexing is taking place.
* [[Image:xref_loc_status_ready.png]] ready, indexing has completed.
* [[Image:xref_loc_status_warning.png]] warning, either the location is empty or a failure occurred trying to access the remote location, if a failure occurred then the reason for failure will have been logged in the '''gravity.log''' or '''xref.log''' which can be viewed by the admin in the Gravity web under settings -> logs.
* [[Image:xref_loc_status_error.png]] error, the location is no longer a managed Xref location (has been deleted).
* [[Image:xref_loc_status_problem.png]] undetermined, the status cannot be checked, either the Xref preference is not in sync with the Xref configuration or the Xref server is unavailable (cannot be reached). Resolve this by updating the Xref preferences. If the preferences are correct but the error persists then check if Gravity and the Xref server can be contacted using the Xref server URL in a web browser. If the server cannot be contacted then this needs to be resolved before continuing with the Xref configuration. If the situation has been corrected, press either Refresh Groups or Refresh Locations to update the status.

Note. A failing location checkout on the Xref server (timeout due to inaccessible host, changed credentials, changed scm software) unnecessarily disrupts normal location checkouts. To avoid reoccurring disruptions, a location will be set to the state suspend after 5 consecutive checkout failures (in the UI the location will have the warning status). The suspend state will ensure that the location will not be checked-out on any following Xref re-indexing cycle. When the location checkout problem has been fixed the location suspend state can be reset to 'no' (in the UI) so that a checkout will take place on the next Xref re-indexing cycle.