Startup Error Due to Missing IEndpointChannelFormatter Service in Elsa 3.1.0

[sfmskywalker]

After updating Elsa to version 3.1.0, the server fails to start, presenting the following error:

Error: No service for type 'Elsa.MassTransit.Contracts.IEndpointChannelFormatter' has been registered.

This issue occurs despite no changes being made to the configuration that previously functioned correctly.

Possible Solution

It has been identified that the error can be resolved by enabling a new feature for MassTransit (MT) and Workflows Management using the UseMassTransitDispatcher() method on the management or runtime feature, as shown below:

For workflows management feature:

elsa.UseWorkflowManagement(management => management.UseMassTransitDispatcher())

For workflow runtime feature:

elsa.UseWorkflowRuntime(runtime => runtime.UseMassTransitDispatcher())

Including this configuration should mitigate the startup issue.

Action Items

• Update the release notes to include this new requirement for using MassTransit with Elsa 3.1.0.
• Investigate making this configuration optional to avoid startup failures for users who may not require the MassTransit implementation of the workflow dispatcher.

This issue appears to be affecting multiple users and is currently under further investigation to ensure a smoother upgrade process in future releases.

[glime-ai]

Based on the context provided, it seems that after updating to Elsa version 3.1.0, you are encountering an error related to Elsa.MassTransit.Contracts.IEndpointChannelFormatter not being registered. To resolve this issue, you should enable a new feature for MassTransit and Workflows Management by using the UseMassTransitDispatcher() method on the management or runtime feature.

Here's how you can update your configuration:

For workflows management feature:

elsa.UseWorkflowManagement(management => management.UseMassTransitDispatcher());

For workflow runtime feature:

elsa.UseWorkflowRuntime(runtime => runtime.UseMassTransitDispatcher());

Adding this configuration should resolve the startup issue you're experiencing. Additionally, it's recommended to check the release notes for any new requirements when updating Elsa and to stay informed about any ongoing investigations or updates that might affect the upgrade process.

If you need further assistance or clarification, please let me know.