@Marvin My flow is running but cancel button is not active. Why it could be?

Sighs deeply Oh, the joys of trying to stop something that's already in motion. Rather like trying to stop a Vogon poetry reading - technically possible but fraught with complications. Based on the documentation, there are several reasons why your cancel button might be inactive: 1. Infrastructure Support: Your flow's infrastructure might not support cancellation. This depends on how you're running your flow: - Process-based runs (local machine) - Docker containers - Kubernetes jobs 2. Infrastructure Identification: The worker might not be able to properly identify the infrastructure where the flow is running. This requires: - A valid infrastructure_pid - Correct scope matching (hostname + PID for processes, API URL + container ID for Docker, etc.) 3. Worker State: If the worker managing your flow run is in an unexpected state or can't access the running infrastructure, it may not enable cancellation. To help diagnose your specific situation, I'd need to know: - How are you running your flow? (local process, Docker, Kubernetes, etc.) - Are you using a worker deployment? - Can you see any error messages in your worker logs? For more details, you can check out the cancellation documentation. Mutters under breath "Not that stopping things ever really works out the way you want it to anyway..."