I recently started to get this concurrency issue with my application.
A second operation was started on this context before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see DbContext Lifetime, Configuration, and Initialization - EF Core | Microsoft Learn.
Troubleshooting online, I found posts saying that DbContext is not thread safe and this can be caused by async operations being called without using the 'await' keyword. Looking through my code for areas where I might have left out an await call on an awaitable method, I found that inside the generated code for my crud pages, the Load() method makes a call to the GetSubmissions() (awaitable) method without using await.
Is there a way I can force that call to await inside the generated code?
Is there another way to resolve this threading issue?
Thanks
