Hi folks, one of our flow runs just failed due to a task run failing with the following message:

Task timed out during execution.

- this is quite unexpected given we don’t have any timeout set on the prefect task, has anyone else encountered this behavior before ?

Hi Marwan, if you don’t have a timeout set on your task then my guess is that your underlying task raised a

TimeoutError

somehow (independently of Prefect); we broadly capture this error and convert it to a

TimedOut

state regardless of whether Prefect raised the error or the underlying task logic raised the error

Hi @Chris White - thank you for the prompt response interesting - so we do have a timeout error in place (as part of the underlying function) but I don’t see the error traceback leading back to our timeout

I think that actually makes sense given the Prefect code path — we capture that error and don’t log it or re-raise it, instead we somewhat quietly wrap it up into a

TimedOut

state. Since this is a built-in exception, we probably should create a custom exception to raise and catch instead so we don’t obscure underlying errors

I see - yep creating a custom exception to raise and catch would certainly help when it comes to debugging

awesome, i’ll open an issue from this thread - should be straightforward to adjust

thank you 👍

@Marvin open “Catching TimeoutError obscures traceback from underlying task”

anytime 👍