jdevillard

ok, I think I've seen the issue. I'll try to propose a fix tomorrow.

Hello @sfmskywalker , during my test , I've seen that issue is due to the `select(x=>x.Id)` in ``` await dbContext.Set().AsQueryable().Where(x => idList.Contains(x.WorkflowInstanceId)).Select(x=>x.Id).AsQueryable().BatchDeleteWithWorkAroundAsync(dbContext, cancellationToken); await dbContext.Set().AsQueryable().Where(x => idList.Contains(x.WorkflowInstanceId)).Select(x => x.Id).AsQueryable().BatchDeleteWithWorkAroundAsync(dbContext, cancellationToken);...

> @sfmskywalker With the latest preview from myget, we getting the following error. Our database is not named Elsa, is the `Elsa.` a accidental missed hardcoded database name in the...

I don't have check the necessary of data at startup, but I've propose some improvements #3286 for the retention module that consist in not retrieving data. Some of the new...

Have you tried with the latest preview version of nuget ?

Same issue for me but I want to be able to load my Blazor WASM from a remote location. loadBootResource works well for all manifest/assembly/pdb etc... but this CustomElements module...

Ok I found the issue about yesterday demo , it was one case when you revert Workflow Configuration to "Default" so the value of the property was LogPersistenceMode.Default and not...

I think this is related to #4701 for my comprehension, return of HTTPEndpoint is done when the workflow is suspended or finished. And at this point, some log & process...

Hello Thanks for this, it seems to fix some part of the issue. Have you do some test on Error handling in the Workflow? If the workflow throw an exception...

> Good point. Perhaps that error handling code needs to check to see if a response is already being sent, and if so, ignore it. In that light, I also...