Hosting Elsa on Multiple Nodes: Executing workflows not working #azureservicebus

Hi,

I have problems with the distributed execution of workflows in Elsa 2.2.1. I configured everything as it is described in the documentation, here is my configuration:

.UseServiceBus(s =>
{
    s.Configurer
        .Transport(t =>
            t.UseAzureServiceBus(
                Configuration.GetConnectionString("ElsaServiceBus"), "ElsaQueue"));
})
.ConfigureDistributedLockProvider(l => { l.UseSqlServerLockProvider(Configuration.GetConnectionString("ElsaServerDb")); })
.UseRebusCacheSignal()
.AddQuartzTemporalActivities(configureQuartz: quartz => quartz.UsePersistentStore(store =>
{
    store.UseJsonSerializer();
    store.UseSqlServer(Configuration.GetConnectionString("ElsaServerDb"));
    store.UseClustering();
}))

The issue is that when I execute some workflow by api it sends an event to the “execute-workflow-definition-request-default” queue and it never reads from this queue to actually execute it.

I found that probably there is incoherency between the QueuingWorkflowDispatcher and the CreateSubscriptions in the queue naming, but maybe there is something more, because I managed to replace the QueuingWorkflowDispatcher with my own implementation but still nothing happens after sending an event to the queue with the “execute-workflow-default” name.

Is something missing in my configuration or is there some bug?

We would like to use Elsa in our company but without distributed nodes, we cannot do it 😦

[progala2]

The fix confirmed. Thanks for your help!

[sfmskywalker]

Could be a bug with the queue names being registered. Will have to investigate.