Here are two scenarios I came across that could cause asynchronization between Vault and FLC.
As you see the revisions are not matching. Because revisions in Vault are bumped when BOM goes from “PDM Released” to “WIP”. So when you revise BOM in FLC, the BOM in Vault is not changing state. I think the “Synchronizing Vault file states based on Fusion Lifecycle items” script should match the revision as well as lifecycle state, it is only synching the lifecycle state.
This scenario is CO issue and cannot be fixed with configuration. In this example both lifecycle state and revision are not synched.
Thank you for the detailed description. If i understood this correctly, the issue is the "Synchronize Change Orders" standard workflow in both cases, is that correct?
Which vaultFLC version are you using?
That is correct, synchronizing change order state and revision. I am using cO 126.96.36.1992
Sorry for the late reply. Can you please try to use vaultFLC 20.0.7? You can download it from the coolOrange Download Zone.