Emulator 60s function timeout

[EthanSK]

[REQUIRED] Environment info

firebase-tools: 15.1.0

Platform: macOS 15.7 (Sequoia), arm64 (Apple Silicon M1 Pro)

[REQUIRED] Test case

Cloud Functions configured with timeoutSeconds: 540 (9 minutes) are being killed by the Firebase Emulator at exactly 60 seconds, ignoring the configured timeout.

// Example function configuration
export const renderClipPreviewVideo = onCall(
  {
    timeoutSeconds: 540,
    memory: '4GiB',
    region: 'us-central1',
  },
  async (request) => {
    // Long-running video rendering operation
  },
);

firebase.json emulator configuration:

{
  "emulators": {
    "functions": {
      "host": "0.0.0.0",
      "port": 5001
    },
    "firestore": {
      "host": "0.0.0.0",
      "port": 8080
    },
    "storage": {
      "host": "0.0.0.0",
      "port": 9199
    }
  }
}

[REQUIRED] Steps to reproduce

1. Create a Cloud Function with timeoutSeconds set to any value > 60 seconds (e.g., 540)
2. Start the Firebase emulators: firebase emulators:start --only functions,firestore,storage
3. Call the function and have it perform an operation that takes longer than 60 seconds
4. Observe the function being killed at exactly 60 seconds with "socket hang up" error

Environment variable workaround attempted (did not work):

export FUNCTIONS_EMULATOR_TIMEOUT_SECONDS=540

[REQUIRED] Expected behavior

The Firebase Functions Emulator should respect the timeoutSeconds configuration specified in the function definition (e.g., 540 seconds), allowing long-running operations to complete within the configured timeout.

[REQUIRED] Actual behavior

The emulator ignores the timeoutSeconds configuration and enforces a hard 60-second timeout. Functions that exceed 60 seconds are killed with the following errors:

⚠  Your function was killed because it raised an unhandled error.
i  Request to function failed: Error: socket hang up

The function is terminated abruptly regardless of:

• The timeoutSeconds value in the function configuration
• The FUNCTIONS_EMULATOR_TIMEOUT_SECONDS environment variable
• Any other configuration attempts

This prevents local development and testing of any function that legitimately needs more than 60 seconds to complete (e.g., video processing, large file operations, AI model inference).

[EthanSK]

Btw, i just want to state how betrayed I feel by the whole firebase emulator experience. As my project grows more complex, the emulators consistently fail to handle the heavier workloads more and more, and I get errors thrown for all sorts of things randomly that are outside my control, that are definitely emulator issue. You really need to work on it, or i'll be forced to move to another solution.

[EthanSK]

Right, that's it. I want you to know how disappointed I am. A company of the world's best engineers supposedly, and you can't even build a functional nodejs wrapper. I am going to run my nest server on pure nodejs locally because at the scale i'm building, I literalyl cannot get anything done with the function emulators. I hope you're proud of your work.

[cabljac]

Hi there, I'm sorry to hear you're having issues with the emulator. Thanks for raising this, I will escalate to the appropriate team.