What are the documented default and maximum durations for a synchronous OCI Functions invocation?
Select an answer to reveal the explanation.
Short Explanation
Sync starts with a 30-second egg timer and you can stretch it only to 300 seconds. Set the timeout near what the work really needs—not the ceiling “just in case.”
Full Explanation
Documented default and maximum durations for a synchronous OCI Functions invocation are a default of 30 seconds and a maximum of 300 seconds. You may raise timeout / timeoutInSeconds above the default, but you cannot push sync past the 300-second ceiling. Best practice for municipal APIs is to set the timeout near actual need rather than always maxing the limit “just in case.”
Default 5 minutes and maximum 24 hours fails by concept because those durations describe other batch-style expectations, not Functions sync limits. Default 300 seconds with unlimited maximum if memory is raised fails because memory and timeout are separate knobs—raising memory does not remove the sync ceiling. Default 1 second and maximum 30 seconds with no overrides fails because the documented default is 30 seconds and you can raise sync up to 300 seconds.
Exam caveat: work that must run longer than sync allows needs detached invoke (with its own ceiling) or a different compute shape such as OKE—not a hidden sync override. Operational check: inspect the function’s timeout setting, load-test the civic handler’s p99 duration, set timeout with headroom under 300 seconds, and alert if invocations approach the limit.