After restoring a company from a backup, the connected program stops communicating even though everything is fine in ABRA Flexi. The cause is usually that the restored company has a different database identifier than the one set in the integration.
Why the identifier changes
Restoring from a backup creates a new company. The identifier is derived from the name, and since the original company with the same name still exists on the server, a number is appended at the end — firma becomes firma1. As a result, the API addresses still point to the original, no-longer-updated company.
Solution
First, list your companies and find the actual identifier of the restored company — it's in the dbNazev field:
GET /c.xml
Then you have two options:
Update the identifier in the integration to the newly created one.
Delete the original company and restore the backup again — without a name conflict, the company will get the original identifier.
⚠️ Before deleting the original company, make sure it doesn't contain newer data than the backup. Deletion is irreversible.
💡 An integration is more resilient when the company identifier isn't hardcoded but stored in the settings instead — after restoring from a backup, you then only need to update a single value.