This message was deleted.

Hi Oscar, you are right. This is actually a common race-condition issue, that people run into. We usually suggest one of the following workarounds: 1. Nest the data from policy source and data updates under different keys (in policy from git that means moving the data.json to a sub folder) 2. Use only one source for data (e.g. drop the data.json file) 3. Use an external data sources confif server to delay the data loading This will be fixed in the next major release of OPAL (the system gets a full rewrite (CC: @Shaul Kremer, @Ro'e Katz). If you want to patch this locally for this version of OPAL, happy to accept PRs and suggest ways to fix.

@Or Weis Thanks for your suggestion.

@Ben Lieber ^^^