Bram Timmers this would work as long as it was not a generic message, and it comes up everytime. If generic it will just drive people to ignore/click on.

If it comes up as a message specific to any 'open' actions (both tasks and approvals), and from there the user can can cancel it, without the need to to go off and review any open actions. It all needs to be within the 'withdrawl' and/or 'cancelation' journey.

I do like the end goal you have mind: to see that irrelevant tasks can be cleaned up, when an asset version gets canceled or even withdrawn. With that end goal in mind, I have a more universal solution in mind, since tasks aren't bound to one specific version (by design). I see more perspective in further improving the 'cancellation' and 'withdrawing' journey, by asking the user at the point where cancels a version, whether he also wants to cancel any of the tasks that are still open. That way, it is a human assessment, whether those tasks are relevant, or not.

Think this one is great, if we can get tasks connection to certain versions!

Assignee unable to complete the action - once job cancelled/withdrawn - to get it off their to-do list.

Same issue for withdrawn jobs.