Skip to content

Workflow cancellation cause is not captured in history #998

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.

Sign up for GitHub

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

Jump to bottom
Open
Ramkumar92 opened this issue May 13, 2025 · 0 comments · May be fixed by #1000
Open

Workflow cancellation cause is not captured in history #998

Ramkumar92 opened this issue May 13, 2025 · 0 comments · May be fixed by #1000

Comments

@Ramkumar92
Copy link

Ramkumar92 commented May 13, 2025 •
edited
Loading

While cancelling the workflow using cadence-java-client, the cause is not captured in history

RequestCancelWorkflowExecutionRequest requestCancelWorkflowExecutionRequest =
    new RequestCancelWorkflowExecutionRequest()
        .setDomain(domain)
        .setWorkflowExecution(new WorkflowExecution().setWorkflowId(workflowId))
        .setCause('Cancellation reason');
workflowClient
    .getService()
    .RequestCancelWorkflowExecution(requestCancelWorkflowExecutionRequest);

When the cancellation is done from cadence web UI the cause is defaulted and visible in workflow history, so this appears to be a bug with cadence-java-client.

This appears to be due the cause not being set in RequestMapper.java
@shijiesheng shijiesheng linked a pull request May 19, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix(RequestMapper): Correctly map all fields shijiesheng/cadence-java-client
1 participant
@Ramkumar92