Skip to main content
All CollectionsIntegrationsTrev + Figured Integration
What can cause a Pending sync status?
What can cause a Pending sync status?
Scott Townshend avatar
Written by Scott Townshend
Updated over 3 years ago

Error message

Description

Suggested action

This Class Change In is pending because the corresponding Class Change Out event has not yet been synchronised with Figured.

A Class Change event in Figured is initiated by Trev transmitting a Class Change Out event. The Class Change In event will remain in a pending state until such time as the Class Change Out event has synchronised.

Ensure the Class Change Out event has been synchronised.

This event is pending because it was previously synced with Figured and has since been deleted in Trev.

This event has previously been synchronised with Figured but has since been deleted in Trev. If you re-sync this event it will remove the event from Figured, and this record will be removed from the Manage Data screen.

Synchronise the event to remove it from Figured.

This Transfer In is pending because the corresponding Transfer Out event for the other farm has not yet been synchronised with Figured.

A Transfer in Figured is initiated by Trev transmitting a Transfer Out event. If you have a Transfer In event this will be in a pending state until such time as the “other” farm synchronises their Transfer Out event.

Wait until the Transfer Out event has been synchronised by the other farm.

This event is pending because it was previously synchronised and has since been updated in Trev.

This event has previously been synchronised with Figured but has since been updated in Trev. If you re-sync this event it will update the event in Figured.

Synchronise the event to update it in Figured.

This event is in the queue to be synchronised.

The Sync Selected or Sync All button has been clicked and this event has been queued but not yet synchronised. NB: you may need to click the “Refresh” button to update the sync status.

Wait for the event to be synchronised. This should only take a few minutes so if the event remains in this state then please contact the Trev support team via Intercom.

Did this answer your question?