Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Occasional case differences occur in the workflow ID, and the lock key does not ignore uppercase, resulting in lock failure #1216

Open
18682788952 opened this issue Nov 28, 2023 · 0 comments

Comments

@18682788952
Copy link

Scenario: Step unexpectedly fails, step is in a failed state, workflow is in a suspended state, and workflow recovery is performed multiple times. Occasionally, there is a problem of repeated execution of failed steps. After source code debugging, it is found that the reason for the locking failure of SingleNodeLockProvider is the lock key ID. Occasionally, there are capitalization issues, resulting in locking failure and repeated execution;

The workflow adopts SQLite persistence;

WorkflowCore" Version="3.9.0
WorkflowCore.Persistence.Sqlite" Version="3.9.0

public class TestStep : StepBodyAsync
{
    public override async Task<ExecutionResult> RunAsync(IStepExecutionContext context)
    {
        await Task.Delay(5000);
        throw new Exception("test error");
    }
}
@18682788952 18682788952 changed the title The lock key does not ignore case, resulting in a difference in case for the workflow ID and causing lock failure 工作流Id偶尔出现大小写差异,锁定键不忽略大写,导致锁定失败 Occasional case differences occur in the workflow ID, and the lock key does not ignore uppercase, resulting in lock failure Nov 28, 2023
@18682788952 18682788952 changed the title 工作流Id偶尔出现大小写差异,锁定键不忽略大写,导致锁定失败 Occasional case differences occur in the workflow ID, and the lock key does not ignore uppercase, resulting in lock failure Occasional case differences occur in the workflow ID, and the lock key does not ignore uppercase, resulting in lock failure Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant