Martin Loetzsch

There's a unfortunately a third place: ```^C Traceback (most recent call last): File "/Users/mloetzsch/Projects/project-a/mara-example-project-2/packages/data-integration/data_integration/execution.py", line 348, in run_pipeline _notify_all(event) File "/Users/mloetzsch/Projects/project-a/mara-example-project-2/packages/data-integration/data_integration/execution.py", line 340, in _notify_all raise e File "/Users/mloetzsch/Projects/project-a/mara-example-project-2/packages/data-integration/data_integration/execution.py", line...

@jankatins are you running that in production? The previous changes you made around cancelling runs really improved things a lot, but here I'm afraid we add a lot of complexity...

@jankatins is this still a problem that justifies the additional complexity?

@jankatins is this running in production?

Hi Jan, where would that button be? And would a click command (then triggered from jenkins or whatever) also do?

Hi @hz-lschick. Is this still a problem?

Ah. A while ago Flask changed how the names of these cli commands get derived from function names. So ```flask mara_pipelines.ui.run_interactively``` became ```mara_pipelines.ui.run-interactively``` You can see all available cli commands...