Possible to save bad flow which runs idefinitely #7387
Labels
area/backend
Needs backend code changes
bug
Something isn't working
kind/customer-request
Requested by one or more customers
Describe the issue
Consider the parent and subflow below. Notice that the type is incorrect, it should be Subflow, not subflow. Kestra UI allows us to save this flow.
The subflow is executed correctly, but the parent flow remains running indefinitely (until manually killed).
What should be the correct behavior here? (stop flow from being saved in the first place, or allow case-insensitive type definition)
Environment
The text was updated successfully, but these errors were encountered: