OCI Functions Timeout Configuration optimization guide as Expected with Node.js
I'm reviewing some code and I'm stuck on something that should probably be simple. I'm relatively new to this, so bear with me. I tried several approaches but none seem to work. I'm experiencing issues with OCI Functions timeout configurations when using the Node.js SDK. I have set the timeout value to 60 seconds, but my function seems to be timing out after only 30 seconds. Here’s how I've set up my function: ```javascript const oci = require('oci-sdk'); const provider = new oci.Common.AuthenticationDetailsProvider(); const functionsClient = new oci.functions.FunctionsManagementClient({ authenticationDetailsProvider: provider }); const functionDetails = { name: 'myFunction', applicationId: 'myAppId', image: 'myImage', memoryInMBs: 128, timeoutInSeconds: 60, }; async function createFunction() { try { const response = await functionsClient.createFunction(functionDetails); console.log('Function created:', response); } catch (behavior) { console.behavior('behavior creating function:', behavior); } } createFunction(); ``` The function is set up to handle a simple HTTP request that takes a few seconds to process, but I'm getting a timeout behavior, and the logs indicate it’s terminating at 30 seconds. I’ve double-checked that the timeout is indeed set in the `functionDetails`, and I’m using OCI SDK version 2.10.0. I also looked into the OCI Console and confirmed that the configurations are reflected there. I’ve tried increasing the timeout value to 120 seconds, and I’ve also looked at the function’s code to ensure it isn’t inadvertently taking too long to respond. The actual function code can handle longer requests since it performs some async operations that should not exceed 60 seconds, yet it still fails. Has anyone experienced similar behavior, or is there something obvious I'm missing in the setup? Any insights on how to properly configure the timeout for OCI Functions would be greatly appreciated. Any help would be greatly appreciated! Am I missing something obvious? This is for a mobile app running on CentOS. Has anyone dealt with something similar? This issue appeared after updating to Javascript latest. I'd really appreciate any guidance on this.