. I have it set to 900 seconds and this is verified in the UI by looking at the block being used by the deployment. I am running Prefect Server 2.11.2. Has anyone else has issues (or success) setting
job_watch_timeout_seconds
and getting it to mark jobs as crashed that exceed the timeout?
Scott Walsh
08/16/2023, 9:12 PM
To clarify, my issue is that the jobs run for longer than 900 seconds and are not marked as crashed, they continue in a Running state.
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.
