@Marvin Hey Marvin, how can I retry a task on specific error codes (500) with the same inputs but using conditional logic based on the number of retries. So if the previous error code was 500 and the current retry count is 2, follow this particular path, otherwise follow the standard path?

It appears that my search for examples of retrying tasks on specific error codes with conditional logic in Prefect 2.x did not return relevant documentation content. However, I suggest consulting Prefect's documentation or community for guidance on this use case, as the practices for implementing retries based on error codes and conditional logic can vary between different versions of Prefect. You might consider writing a custom retry logic within a Prefect task where you catch the exceptions and implement your own logic to determine whether to retry the task and how exactly to handle various retry counts and error codes. It's possible to combine the catching of specific exceptions—in your case, HTTP error codes like 500—with a counter that you increment each time the task retries. You can then branch the logic based on the current retry count and the specific error caught. I apologize for not being able to provide a direct code example or documentation link at this time. If you need further assistance, please consider reaching out to the Prefect community or support, or explore Prefect's official documentation: Prefect Docs, where you can find more detailed guidance on task retries and error management.