Does SQL Developer automatically synchronize metadata after external schema changes?

SQL Developer utilizes an internal metadata cache to store table structures, constraints, and triggers within the Connections navigator and object browser. However, when schema objects are modified via external clients—such as command-line tools or other IDEs—the interface often persists displaying outdated column definitions or indexes.

While a manual 'Refresh' command exists for specific nodes, there appears to be no documented global background auto-refresh mechanism for the object tree. This leads to a discrepancy where the user may attempt to execute queries based on visible metadata that no longer exists in the live database dictionary.

Is there a configuration setting to adjust the frequency of metadata re-validation for the object tree? How does the code completion cache size interact with the synchronization of the UI-bound schema components?