Configuration for timing out node attempts.
Timeouts rely on asyncio cancellation. If your node uses synchronous time.sleep() or other CPU-bound work that blocks the GIL, the timeout will not be fired until after the event loop has been released.
Under refresh_on="auto", an internal handler refreshes the timeout on any
callback event that occurs in the execution of the node or its nested descendants.
Hard wall-clock cap (in seconds) for a single node attempt.
This timeout is never refreshed by progress signals or runtime.heartbeat().
Maximum time (in seconds) a single node attempt may go without observable progress.
Which signals refresh idle_timeout.
"auto" refreshes on standard graph progress signals and explicit heartbeats.
"heartbeat" refreshes only on explicit runtime.heartbeat() calls.
Normalize a timeout value to positive-second policy fields.
