Firstly we would need to see what the actual error is then click on the line that has the error and look at the properties window (vertical window on the right).
But if it just starts working, then usually it means either
1) some value that is being used to filter those data loads isn't set yet so it fails, then it gets set based on something happening and so it starts working
2) well, its usually #1. If they don't have permissions then it won't ever work, so I have to suspect either incredibly slow data loads or a dependency necessary isn't loaded (a record hasn't been selected, a primary Field that everything filters on isn't populated yet, the collections are not built yet).
Since it starts working after some... after freshes(which I do not know if you mean you CTRL F5'd, or restarted the app a few times, or your browser etc), it can mean things are finally getting cached so it works.
Would have to see your actual expressions and configuration for any of the items not working. I also saw the error that says the one value is not correct. If your filters are looking at that value and its incorrect, then the rest will fail until its correct.
Please share the configuration of your AppOnStart and the configuration of any of the Controls that are failing to load the data.
Also depending on if you have don't load until visible etc (or maybe you should turn it on), there are still many thoughts around why it happens. But the monitor clearly tells you there is an issue, but you need to load at the properties to get more details.
You can even turn on Verbose mode to get deeper details
