Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hello one question. I set up a 1800 second timeout for a task, but it got stuck and didnt finish after that time out, it kept on waiting for hours and hours.
```@task(log_stdout=True, state_handlers=[handler], timeout=1800)```

Hi <@U01LQSQV3ST>, what is that task doing? This seems like something in the task was hanging

i am hitting an api that sometimes takes quite a bit to het the 200 http status. i want to fail the flow if it takes more than the specified time.

This seems like it should work. I’d have to check with the team and get back to you on Monday.

awesome man,, im goingt o try with shorter timeouts and test a little, thanks man!!

Sorry I forgot to ask the team today. Will leave a message with them and get back to you tomorrow.

Did you try the shorter timeouts and see the same behavior?

i did a short 10 second timeout, and it stopped like it should

Hey <@U01LQSQV3ST> -- could you try turning on DEBUG level logs with the long timeout? Timeouts are a bit complicated and the logs will help us figure out where it's hanging. Could you also provide the output of `prefect diagnostics` ?

```{
  "config_overrides": {
    "cloud": {
      "agent": {
        "auth_token": true
      }
    },
    "context": {
      "secrets": false
    }
  },
  "env_vars": [],
  "system_information": {
    "platform": "Linux-5.4.0-51-generic-x86_64-with-glibc2.29",
    "prefect_backend": "cloud",
    "prefect_version": "0.14.12",
    "python_version": "3.8.5"
  }
}```

ok i set up the debug level, once i get the error , i will send you the logs

There's also a fix in 0.14.16 for some edge-case timeout issues <https://github.com/PrefectHQ/prefect/pull/4384>

image.png

ok 30 minutes have passed and no luck with the timeout

it was running that checking flow run state every 4 seconds and then it stopped

( i am not multithreading and the ram and cpy usage seem normal)

Hey <@U01LQSQV3ST> -- could you share the logs when the task is set up? There should be some things about timeout handling