cfy executions start -w my_execution
If my_execution is defined in the blueprint, but leads to a nonexistent Python module/function, an exception will be shown to the management worker logs. However, from that point on, there is no way to remove the execution. Cancellation or force-cancellation won't help (execution will be stuck in cancelling or force_cancelling state).
This will also happen if the python module being invoked encounters an interpretation exception before the workflow itself is called. For example:
This will bring the execution to "pending" state because of the division by zero.
Another example steps to reproduce
1. Declare a plugin that exists within the blueprint (under `plugins/`), but remove the actual plugin implementation files
2. Run the my_workflow workflow