For a detached OCI Functions invocation that should not block the caller, what is the documented upper bound for detachedModeTimeoutInSeconds?
Select an answer to reveal the explanation.
Short Explanation
Detached can wait longer than sync—up to an hour—but it is still a function, not a days-long batch farm. Multi-hour or always-on work belongs elsewhere.
Full Explanation
For a detached OCI Functions invocation that should not block the caller, the documented upper bound for detachedModeTimeoutInSeconds is one hour (3600 seconds), with a configurable range from 5 to 3600 seconds. Detached returns to the caller once processing has begun, while the function may continue up to that configured detached timeout. That fits civic fire-and-continue workflows that still fit inside an hour—not multi-day batch farms.
Thirty seconds identical to the sync default with no raise allowed fails by concept because detached timeout is separately configurable up to 3600 seconds and is not frozen at the sync default. Seven days matching Object Storage lifecycle rules fails because Object Storage lifecycle retention is unrelated to Functions execution limits. Unlimited duration as long as the application uses a regional subnet fails because subnet HA choices do not remove the detached timeout ceiling.
Exam caveat: unset detached timeout may fall back to sync timeout behavior—explicitly set detachedModeTimeoutInSeconds when you need the longer window, and never assume multi-day Functions runtimes. Operational check: configure detached timeout for the workload, invoke detached from a non-blocking caller, confirm the client returns promptly, and verify the function completes within the configured hour bound in logs/metrics.