Exception when starting activity with HTTP Endpoint

Latest source compiled and Monolith started. Simple workflow with HTTP Endpoint and response.

I get following exception when triggering endpoint:

Elsa.Exceptions.LockAcquisitionException: Failed to acquire a lock on correlation ID at Elsa.Dispatch.Handlers.ExecuteWorkflowDefinition.Handle(ExecuteWorkflowDefinitionRequest request, CancellationToken cancellationToken) in D:\Projects\Envox\Mainline\ThirdParty\elsa-core\src\core\Elsa.Core\Dispatch\Handlers\ExecuteWorkflowDefinition.cs:line 63 at MediatR.Pipeline.RequestExceptionProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at MediatR.Pipeline.RequestExceptionProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at MediatR.Pipeline.RequestExceptionActionProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at MediatR.Pipeline.RequestExceptionActionProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at MediatR.Pipeline.RequestPostProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at MediatR.Pipeline.RequestPreProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at Elsa.Dispatch.Handlers.TriggerWorkflows.StartWorkflowsAsync(TriggerWorkflowsRequest request, CancellationToken cancellationToken) in D:\Projects\Envox\Mainline\ThirdParty\elsa-core\src\core\Elsa.Core\Dispatch\Handlers\TriggerWorkflows.cs:line 96 at Elsa.Dispatch.Handlers.TriggerWorkflows.Handle(TriggerWorkflowsRequest request, CancellationToken cancellationToken) in D:\Projects\Envox\Mainline\ThirdParty\elsa-core\src\core\Elsa.Core\Dispatch\Handlers\TriggerWorkflows.cs:line 82 at MediatR.Pipeline.RequestExceptionProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at MediatR.Pipeline.RequestExceptionProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at MediatR.Pipeline.RequestExceptionActionProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at MediatR.Pipeline.RequestExceptionActionProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at MediatR.Pipeline.RequestPostProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at MediatR.Pipeline.RequestPreProcessorBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) at Elsa.Activities.Http.Middleware.HttpEndpointMiddleware.InvokeAsync(HttpContext httpContext, IMediator mediator) in D:\Projects\Envox\Mainline\ThirdParty\elsa-core\src\activities\Elsa.Activities.Http\Middleware\HttpRequestMiddleware.cs:line 28 at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider) at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

Please advise what did I do wrong?

[sfmskywalker]

It’s not you; it’s me. I will fix.

[sfmskywalker]

Fixed the path in the other project as well 👍🏻 Regarding .NET 6.0, there’s no special reason. I installed the .NET 6.0 preview bits, which causes it to be the default SDK when creating new projects. It’s OK to change it to .NET 5.0.