@Bianca Hoch retries is good, we can mention in the code that this task should retry itself this many number of times, and after these mentioned retries if it fails then it will be marked as crashed. And I can't see any button to restart this specific task.
In our case flows are going to be very large, a lot of times it happens multiple tasks get failed in the run, because of some unhandled errors can be different for each task. Now before we even get to identify the issue the max retry limit exceeds or lets say I have fixed the issue and I want this task to run immediately, or lets say the task and all its downstream tasks are completed but they ran reading old configurations (configs we store in shared files) and now after updating my configurations I want to re-run this successful task and all its downstream tasks.
In Prefect 1 it was pretty easy to do so, there was a restart button for every task and flow and we just hit that button for restarting that task doesn't matter in which state it is failed, successful, or whatever, and all its downstream tasks restarts as well.