vegaprotocol
[Bug]: Candle data incorrect after second load from network history
Problem encountered
Nodes guru loaded up a fresh datanode using network history, due to the volume of data in the first load they then started a second network history load after the first had finished to bring the datanode up-to the latest height (mimicking the functionality recently automated by adding a loop in the load). After the second load, candle data prior to the data being loaded was no longer available (note, unable to confirm if it was available prior to the second load), despite the relevent trades data being present in the trades table.
Querying the database confirmed that the candle data is not available in the candle cagg views. Manually refreshing the candle data using the 'refresh_continuous_aggregate' timescale function with both null args for start and end time and explicit start and end times did not resolve the issue, candle data prior to the 2nd load was still not present in the cagg views.
Observed behaviour
"
Expected behaviour
"
Steps to reproduce
"
Software version
0.72.14
Failing test
No response
Jenkins run
No response
Configuration used
No response
Relevant log output
No response
