| User Roles |  Admin |  Staff contributor | ✗ External Contributor | ✗ Pulse user |
This article explains common synchronisation issues between Silverfin and Horus and provides guidance on resolving them.
Table of contents
Credentials related errors
Error:
We were unable to connect to Horus. The token or access used is no longer valid. Please create a new Horus sync entity at firm level to reconnect with Horus and then transfer this file there.
Explanation:
This error indicates that the credentials used no longer have access to the relevant Horus files.
What can you do:
- Reconnect synchronisation at the firm level. Note: Only users with admin rights can perform this action. For detailed steps, refer to: How to reconnect (re-authenticate) synchronisation with Horus?
Other errors
Error:
Alternate language not selected, please check the configuration in Horus and try again.
Explanation:
The languages in Horus are not configured correctly.
What can you do:
- In Horus, go to the Client File Identification section and make sure both the primary and alternate languages are specified.
- make sure you don't choose 'Other' as a primary language.
Transaction booked in Horus missing in Silverfin
Horus only sends transactions that are marked as confirmed. Silverfin can only fetch these confirmed transactions.
What can you do:
- If you notice missing transaction(s) in Silverfin, verify that they are confirmed in Horus.