Radom exception failures with: Non-Deterministic workflow detected: A previous execution of this orchestration scheduled an activity task with sequence ID 1 ... but the current replay execution hasn't (yet?) scheduled this task. Was a change made to the orchestrator code after this instance had already started running? #2910
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are seeing this random failure in our services, there is no code change happening when we get this failure. Can anyone give some suggestion on what to look for this issue?
The orchestration code is like this:
// Acquire thread lock.
while (input.Status == ThreadMigrationStatus.NotStarted || input.Status == ThreadMigrationStatus.AcquiringLock)
{
input = await context.ScheduleWithRetry(
typeof(AcquireThreadLockActivity),
GlobalDTFSettings.DTFCustomRetryOptions,
input).ConfigureAwait(true);
if (input.Status == ThreadMigrationStatus.AcquiringLock)
{
// 30s interval.
await context.CreateTimer<object?>(context.CurrentUtcDateTime.AddSeconds(30), null).ConfigureAwait(true);
}
}
Beta Was this translation helpful? Give feedback.
All reactions