On MANY specific actions, there is a tickbox "Continue after error" and also, you might choose to only trigger those actions throwing errors WHEN the conditions are met. If the conditions are not met, and the errors will occur, simply skip the action entirely (You could use For loops to slot off certain action sets from running.)
Instead of errors throwing and tasks stopping and "unnecessary vibrations" happening, you are the one responsible for "error handling" in your own tasks. While you CAN brute force stop some error notifications, it would certainly be foolish for nearly all users to not have those notifications when building and running tasks. Not knowing the errors would interrupt the task building process so completely the workflow determined over the years is you handle the errors one by one or class by class and THEN you will get no errors in your tasks. It certainly makes sense to stop some individually, so my opinion is keep doing that instead of disable notifications the system and user usually assume are "necessary" for problem solving.
Once I solve my task errors, they typically run without fail and I only ever get errors messaging in the real edge cases, not the ones I come to anticipate (and so "error handle").