After adding a heavier library, a Java Oracle Function for tax-roll transforms begins returning FunctionInvokeTimeout / 504 even though wall-clock work used to finish. What should the team check first among Functions settings?
Select an answer to reveal the explanation.
Short Explanation
A cramped desk makes every task look “slow” until the clock runs out. Undersized memory—especially for Java—can burn the whole timeout window on GC, so bump memory steps before assuming the timeout value alone is wrong.
Full Explanation
Official troubleshooting notes that a 504 or FunctionInvokeTimeout on invoke is often cured by raising memory, particularly for Java, not only by raising timeout. A handler spending the window on garbage collection or memory pressure appears slow to the caller. After dependency changes, verify memory configuration against the discrete official steps first.