www.inngest.com Open in urlscan Pro
76.76.21.61  Public Scan

Submitted URL: https://www.inngest.com/docs/faq#why-am-i-getting-a-function-invocation-timeout-error
Effective URL: https://www.inngest.com/docs/faq
Submission: On February 14 via api from US — Scanned from DE

Form analysis 0 forms found in the DOM

Text Content

Docs
Search...Ctrl K

Docs
 * Docs
 * Patterns

Star our open source repoJoin our Discord communityFollow us on X.com


Sign InSign Up
 * Home
 * Getting started
 * Guides
 * Platform


 * SDK REFERENCE
   
   * TypeScript
   * PythonBeta
   * GoBeta


 * API
   
   * REST APIIn progress


 * HELP
   
   * FAQs
   * Status Page
   * Support Center
 * Sign InSign Up


FREQUENTLY ASKED QUESTIONS

 * How do I run crons only in production?
 * How do I stop functions from running?
 * Why am I getting “Event key not found" errors in branch environments?
 * How do I specify multiple serve paths for a same Vercel application on the
   Dashboard?
 * What's the recommended way to redact data from step outputs?
 * Why am I getting a FUNCTION_INVOCATION_TIMEOUT error?
 * My app's serve endpoint requires authentication. What should I do?
 * Why am I getting a NON_DETERMINISTIC_FUNCTION error?


HOW DO I RUN CRONS ONLY IN PRODUCTION?

There are multiple ways to achieve it:

 1. Conditionally rendering depending on the environment.

process.env.NODE_ENV === "production" ? { cron: "* * *" } : { event: "dev/manualXYZ" }


CopyCopied!

đź’ˇ If you render an event instead of a cron in the other environments, you can
still trigger your functions manually if needed.

 2. Disable branch environments.


HOW DO I STOP FUNCTIONS FROM RUNNING?

The best way to ensure a deprecated function doesn't run is to deploy without
including it in your serve handler. You can temporarily achieved the same result
by archiving the function on our dashboard, but note that a new deployment will
unarchive the function.


WHY AM I GETTING “EVENT KEY NOT FOUND" ERRORS IN BRANCH ENVIRONMENTS?

Branch environments are automatically archived 3 days after their latest deploy.
It's possible to disable the auto archive functionality for each active
environment on our dashboard.


HOW DO I SPECIFY MULTIPLE SERVE PATHS FOR A SAME VERCEL APPLICATION ON THE
DASHBOARD?

You can pass multiple paths as comma-delimited values under the Vercel app in
the Vercel Integration’s settings.


WHAT'S THE RECOMMENDED WAY TO REDACT DATA FROM STEP OUTPUTS?

We recommend doing E2E encryption instead, as it's more secure and plaintext
data never leaves your servers.


WHY AM I GETTING A FUNCTION_INVOCATION_TIMEOUT ERROR?

This is a Vercel error that means your function timed out within Vercel's
infrastructure before it was able to respond to Inngest. More information can be
found in Vercel's docs.

If you're unable to sufficiently extend the timeout within Vercel, our streaming
feature can help.


MY APP'S SERVE ENDPOINT REQUIRES AUTHENTICATION. WHAT SHOULD I DO?

Your app's serve endpoint needs to be accessible by our servers, so we can
trigger your functions. For this reason, we recommend disabling authentication
for the serve endpoint.

Our servers communicate securely with your app's serve endpoint using your
signing key.


VERCEL

By default, Vercel enables Deployment Protection for both preview and generated
production URLs. This means that your app's serve endpoint will be unreachable
by our servers unless you disable Deployment Protection or, if you're on
Vercel's Pro plan, configure protection bypass.


WHY AM I GETTING A KILLED ERROR WHEN RUNNING THE DEV SERVER?

This is likely an npx issue, which can be solved by running rm -rf ~/.npm/_npx.
If the error still persist, please reach out to us on our Discord.


WHY AM I GETTING A NON_DETERMINISTIC_FUNCTION ERROR?

This is an error present in v2.x.x of the TypeScript SDK that can be thrown when
a deployment changes a function in the middle of a run.

If you're seeing this error, we encourage you to upgrade to v3.x.x of the
TypeScript SDK, which will recover and continue gracefully from this
circumstance.

For more information, see the Upgrading from v2 to v3 migration guide.

PreviousREST API

© 2024 Inngest Inc. All rights reserved.

Star our open source repoJoin our Discord communityFollow us on X.com