CodexBloom - Programming Q&A Platform

OCI Functions: Timeout implementing Long-Running Tasks in Node.js Lambda Functions

šŸ‘€ Views: 0 šŸ’¬ Answers: 1 šŸ“… Created: 2025-06-26
oracle-cloud functions nodejs Node.js

After trying multiple solutions online, I still can't figure this out. This might be a silly question, but I'm stuck on something that should probably be simple. I'm currently working with Oracle Cloud Infrastructure Functions and I've encountered a question with timeout settings when running long tasks. My function is meant to process large data files, but it seems to hit a timeout limit after 60 seconds, even though I've set the timeout configuration to allow for 180 seconds. Here's a snippet of my `func.yaml` configuration: ```yaml version: 1.0 name: my-function image: my-function-image memory: 256MB timeout: 180s ``` Despite this configuration, I'm receiving the following behavior in my logs: ``` Function execution timed out after 60 seconds ``` I've also tried modifying the timeout settings directly in the OCI Console, and I've confirmed that the configuration is being correctly deployed. When I run the function locally using the `fn invoke` command, it works as expected without hitting any timeouts. However, once deployed, the question continues. I've double-checked that I’m using the latest version of the `fn` CLI (v0.7.0) as well as the `@fnproject/spec` Node.js package (v1.0.0). I've also consulted the OCI documentation but didn't find anything on this specific scenario. Has anyone else experienced similar timeout problems when using OCI Functions with Node.js? Any insights or solutions would be greatly appreciated! What am I doing wrong? Thanks in advance! For context: I'm using Node.Js on Windows. For context: I'm using Node.Js on macOS. Am I missing something obvious?