The deployed fix, although addressing a real issue that would've popped up, is actually unrelated to the issue you raised and after further investigation it might even be redundant...
I think I found the reason for it just now:
These vaults have been deployed to Goerli network (ethereum-2 in Axelar is goerli) and the VaultCreated event that was supposed to be caught and processed by Subgraph was emitted on Goerli network.
This means that:
Subgraph on Mumbai didn't catch VaultCreated event (emitted on Goerli) and thus didn't create Vault entities
when strategy parameters were set on the Registrar (and corresponding event was emitted), Subgraph created the Strategy entity
since there were no Vault entities in Subgraph, there was nothing to tie to newly created Strategy
vaultLocked and vaultLiquid remained null
This can be addressed like the following:
Strategy will be updated to have a field that stores only vault addresses (instead of having a direct relationship to Vault entity) -> this way updating strategy params will be correctly registered by Subgraph
when data of the Vaults tied to some Strategy is necessary, the client can query the appropriate network (indicated by strategy.network) to fetch Vault entities queried by addresses stored in Strategy
\@SovereignAndrey we might need to deploy a Subgraph to Goerli to be able to query event data emitted on this network. However this is not yet required (though it might become necessary at some point) - vault data can easily be queried directly on-chain using addresses (to be) stored in Strategy entity (as described above)
From Discord: