Desynchronization of the "Custom Properties" field between openmetadata nodes

[robogiar]

Good evening! Please tell me if this is the expected behavior: we have two open metadata nodes deployed, if I create a new "Custom Properties" through the UI and fill it in for any table, then when accessing the API to the second node, I get an error: "test_field instance for table not found" - 404. If I change the value of an existing "Custom Properties", then there are no problems. I've been trying to find information about the cache, but to no avail.