issue with _alterationPlanScheduler.SubmitAsync after mutitenanet enabled

[shouha85]

any one has idea how await _alterationPlanScheduler.SubmitAsync(plan); will work under specific tenanet
as the following error thrown when i use the above method after "using (_tenantAccessor.PushContext(tenant))", knowing it work just fine without the tenanet configure

System.Exception: Workflow definition with ID 'Elsa.Alterations.ExecuteAlterationPlan' not found
at Elsa.Alterations.Services.DefaultAlterationPlanScheduler.SubmitAsync(AlterationPlanParams planParams, CancellationToken cancellationToken)

I saw in the "ExecuteAlterationPlanWorkflow " class we have the below cont string, but after configure tenanet (with 2 tenanets) in Elsa 3.5 i have now 3 ExecuteAlterationPlan (tenant-2:Elsa.Alterations.ExecuteAlterationPlan, tenant-1:Elsa.Alterations.ExecuteAlterationPlan, Elsa.Alterations.ExecuteAlterationPlan)
so when i push the target tenanet like "tenanet-1" the engine will not find "Elsa.Alterations.ExecuteAlterationPlan" definition
internal const string WorkflowDefinitionId = "Elsa.Alterations.ExecuteAlterationPlan";

please advise

i have check the code and i think the issue is both "DefaultAlterationPlanScheduler, DefaultAlterationJobRunner" isn't aware of tenant,
how we can fix this issue ..

[StevenMcCawley]

I'm not sure if youre using entity framework, but I am and I just ran into this issue as well. For Entity Framework, I'm sure the proper fix is to fix (or create a new) the migration that inserts the {tenant-id}:Elsa.Alterations.ExecuteAlterationPlan definition. Not only is the tenant id here unnecessary (its in the Id and the tenantId field), but it will actively throw this error. I changed the DefinitionId in my table and the alteration plan schedule began to work.

[StevenMcCawley]

@sfmskywalker

[StevenMcCawley]

Or, Create youre own implementation of IAlterationPlanScheduler and register it ST it is tenant-aware