# Cancel continue-as-new workflow
**URL:** https://community.temporal.io/t/cancel-continue-as-new-workflow/13272
**Category:** Community Support
**Tags:** go-sdk
**Created:** [August 24, 2024, 1:12pm UTC](https://community.temporal.io/t/cancel-continue-as-new-workflow/13272 "2024-08-24T13:12:00Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Alexey\_Prokopov](https://community.temporal.io/u/Alexey_Prokopov)
#### Post date: [August 24, 2024, 1:12pm UTC](https://community.temporal.io/t/cancel-continue-as-new-workflow/13272/1 "2024-08-24T13:12:00Z")
Hi,
I encountered unusual behavior when canceling a “Continue as New” workflow. When the parent workflow is canceled, the child workflow is also canceled if it hasn’t been started as a “Continue as New” workflow. However, if the child has already restarted as a “Continue as New” workflow, the cancellation doesn’t occur.
1. Could you explain why this happens?
2. How can I handle the cancellation of child workflows in this case?
---
### Author:  [@maxim](https://community.temporal.io/u/maxim)
#### Post date: [August 24, 2024, 2:42pm UTC](https://community.temporal.io/t/cancel-continue-as-new-workflow/13272/2 "2024-08-24T14:42:30Z")
I cannot reproduce the problem. Look at the parent workflow history for `ExternalWorkflowExecutionCancelRequested`. And for `WorkflowExecutionCancelRequested` in the child workflow history.
My guess is that the child doesn’t handle the cancellation request properly.