I dont think this happened to me locally. Logs are from production environment.
At application start (run after new deploy or if application was shut down/sleep due inactivity) this error sometimes occurs. It seems random, we can't reproduce it.
hi
- Steps to reproduce the issue:"
Run the application. Let application shut down and then random once in x app inicializations this happens.