OCI Functions: Timeout implementing Long-Running Background Jobs Using Node.js
I keep running into I tried several approaches but none seem to work. I'm currently developing a serverless application using OCI Functions with Node.js, and I'm working with a frustrating timeout scenario when executing long-running background jobs. My function is intended to process large datasets, but it often exceeds the default timeout limit of 60 seconds, resulting in the behavior: `Function execution timed out`. I've tried increasing the timeout in the `function.json` configuration file, but it seems to revert to the default value when I deploy the function. Here’s the relevant part of my configuration: ```json { "version": "0.0.1", "name": "myFunction", "runtime": "nodejs:14", "timeout": 120 } ``` When I deploy the function with the `fn deploy` command, it doesn't seem to accept the timeout parameter. I also attempted to specify it directly in the deployment command as follows: ```bash fn deploy --timeout 120 ``` But I still receive the same timeout behavior. I’ve checked the OCI documentation, and it appears that the maximum timeout for a function is 900 seconds, which should be sufficient for my use case. I also verified that my OCI CLI is updated to the latest version (2.24.0). Additionally, when I try running the function locally using `fn run`, it works without any issues, but the timeout only becomes apparent after deploying it to OCI. Can anyone provide insights on why the timeout setting isn't being respected in the cloud environment? Is there any other configuration I might be missing, or is this a limitation of OCI Functions that I need to work around? Any help would be appreciated! My development environment is Windows. I'd really appreciate any guidance on this. Am I approaching this the right way?