You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently migrated our periodic workflows from the DTF library to the latest Microsoft.Azure.DurableTask.AzureStorage (v2.0.0) due to security compliance. However, existing periodic workflows are no longer triggering. Though when we check status for periodic workflow , it always shows in running state.
The issue seems to be related to the migration to v2.0.0 of the Azure Storage provider. Older periodic workflows might have compatibility issues.
Observations:
No errors or exceptions are logged.
Request:
Please investigate this potential compatibility issue and suggest solutions to restore scheduled trigger functionality for existing workflows
The text was updated successfully, but these errors were encountered:
keshari
changed the title
Periodic Workflow is not triggered after set period when migrated to .Microsoft.Azure.DurableTask.AzureStorage" Version="2.0.0"
Periodic Workflow is not triggered after migration to .Microsoft.Azure.DurableTask.AzureStorage" Version="2.0.0"
Aug 15, 2024
I've reviewed the logs provided, but they did not include the necessary logs from DurableTask-AzureStorage.
I also requested code from @keshari and reproduced the workflow on my end by creating an orchestrator instance with a Timer and ContinueAsNew. I first used DTFx.ASv1.17.3, then continued the same orchestrator instance with DTFx.AS v2.0.0, and it worked as expected with no issue. So, I'm requesting @keshari to share logs with the relevant information again for further investigation.
Also, asked @keshari to downgrade DTFx.AzureStorage ver to v1.17.4 first as they were using a old version as v1.12, to see if the issue can be mitigated/instance continue running.
Hi Team,
We recently migrated our periodic workflows from the DTF library to the latest Microsoft.Azure.DurableTask.AzureStorage (v2.0.0) due to security compliance. However, existing periodic workflows are no longer triggering. Though when we check status for periodic workflow , it always shows in running state.
Code Snippet:
C#
public sealed override async Task RunTask(OrchestrationContext context, TInput input)
{
// ... existing logic ...
finally
{
await context.CreateTimer(DateTime.UtcNow.Add(this.Periodicity), null);
context.ContinueAsNew(input);
}
}
Suspected Cause:
The issue seems to be related to the migration to v2.0.0 of the Azure Storage provider. Older periodic workflows might have compatibility issues.
Observations:
No errors or exceptions are logged.
Request:
Please investigate this potential compatibility issue and suggest solutions to restore scheduled trigger functionality for existing workflows
The text was updated successfully, but these errors were encountered: