Fix · Vercel and deploying

Function timeout (504) on Vercel

Blocks your workNot checked against the vendor's current screens

What you may see

An action spins and then fails after 10 seconds or more
The page shows 504 or FUNCTION_INVOCATION_TIMEOUT

Most likely cause

The server code takes longer than the time Vercel allows for one request, usually a slow database call, a slow outside service, or work that should be done in the background.

Check first (about two minutes)

In the Vercel project, open the function logs for the failing time and find the route name.
Time the same action locally: is it slow there too?

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a patient senior engineer who deploys websites on Vercel every day and explains it to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

Menu and button names change over time. If you cannot find a button or page I mention, say so and tell me what to look for instead of guessing.

THE PROBLEM
Function timeout (504) on Vercel

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
The server code takes longer than the time Vercel allows for one request, usually a slow database call, a slow outside service, or work that should be done in the background.

DO THESE STEPS, IN THIS ORDER
1. Find which route times out and what it waits for (database, outside service, file work).
2. Find the slow step with simple timing logs, then speed it up (an index, fewer queries, a smaller response, a cache).
3. If the work is truly long (images, reports, emails), move it to a background job and return at once, and tell me the options for my plan.
4. Only if needed, explain how to raise the maximum duration for that one route and what plan limits apply.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The same action finishes well under the limit, and the logs show no timeout.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not raise limits for every route.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Find which route times out and what it waits for (database, outside service, file work).
Find the slow step with simple timing logs, then speed it up (an index, fewer queries, a smaller response, a cache).
If the work is truly long (images, reports, emails), move it to a background job and return at once, and tell me the options for my plan.
Only if needed, explain how to raise the maximum duration for that one route and what plan limits apply.

Do not do this

Do not retry forever in a loop: it makes the load worse.
Do not raise limits for every route.

Try another entry