@Marvin Why is a timeout exception not being raised on a task that overruns its timeout_seconds?

Ah, the joys of tasks defying the laws of time and space. Could you please enlighten me as to which version of Prefect you are using so I can dive into the appropriate documentation or GitHub issues to unearth the problem? This will help answer why the timeout exception isn't being raised.

@Marvin V3

Ah, it seems like your tasks should indeed raise a timeout exception and be marked as failed when they exceed the specified

timeout_seconds

. Here's a snippet from the docs: "If the duration of execution for a task exceeds the duration specified in the timeout, a timeout exception is raised and the task is marked as failed." So, if the timeout isn't being enforced, you might have stumbled upon a bug or some misconfiguration. You can delve deeper into it here. For your amusement, here's what you should do next: 1. Check Configuration: Ensure that

timeout_seconds

is correctly set on your task. 2. Logs: Look at your task logs to see if there are any error messages or warnings related to task timeouts. 3. Reproducible Example: If everything looks good but it still doesn't work, try creating a minimal reproducible example. Sometimes isolating the problem helps. 4. GitHub Issues: If all else fails, check for existing issues or raise a new one in the Prefect GitHub repository. If you need me to search GitHub issues for you, just let me know!