(local database)
(the command was not executed it was an update of the record by another server)



I know I have an older version.

This is the first such bug since I have this version, so I can't check if it will appear in the new version because it occurred in a random situation.

Has it been repaired in a new one?
Maybe it is about that, but I'm not sure.

• Add timeout for command executions
• Improve Vault sync lookup error message

1. Please follow the issue template.
2. Please read the issue template - it makes it very clear that you should try updating before reporting an issue.