---
title: "Troubleshooting Functions"
description: "Fix Functions problems activating, deploying, calling, timing out, and deactivating, from the message you see."
content_type: "troubleshooting"
product: "functions"
platform: "MyAccount"
url: "/myaccount/functions/troubleshooting/functions/"
relationships: {"troubleshooting-for":["/myaccount/functions/how-to/activate-functions/","/myaccount/functions/how-to/create-a-function/","/myaccount/functions/how-to/upload-code-as-a-zip/","/myaccount/functions/how-to/call-a-function/","/myaccount/functions/how-to/edit-a-function/","/myaccount/functions/how-to/delete-a-function/","/myaccount/functions/how-to/deactivate-functions/"]}
---

# Troubleshooting Functions

Find the message you see when you activate Functions, create or call a function, or read its
logs. A function's **Status** in the Functions list and its **Build Logs** tab are the first
places to look when a function fails to deploy.

## Credit are not sufficient

If your account is prepaid, activating Functions needs a balance that covers the CPU monthly
minimum. With less, activation stops at "Credit are not sufficient."

Add balance to your prepaid account, then activate Functions again. See
[Activate Functions](/myaccount/functions/how-to/activate-functions/).

## Your function code does not adhere to the E2E Function format as suggested, please review your code.

This message appears when you create a function whose required files are missing or misnamed. It
also appears for a ZIP whose files sit at the top, with no root directory. That ZIP passes the
upload check and is refused only when you click **Create**.

Check that the ZIP has a single root directory and contains the runtime's required files under
their exact names. See [Upload code as a ZIP](/myaccount/functions/how-to/upload-code-as-a-zip/).

If you wrote the code in the editor, keep the code file and the requirements file under the
runtime's names. See
[Runtimes and hardware](/myaccount/functions/concepts/runtimes-and-hardware/#language-runtimes).
Code too large for the editor's 50 MB ZIP gets a different message. See
[Generated ZIP exceeds the 50MB limit](#generated-zip-exceeds-the-50mb-limit).

The rejected function still appears in the list as **Failed**. To create
the function again under that name, delete the failed one first, or choose a different name. See
[Delete a function](/myaccount/functions/how-to/delete-a-function/) and
[Function with name {name} already exists](#function-with-name-name-already-exists).

## Function with name {name} already exists

You tried to create a function with a name that one of your functions already uses. The message
shows that name in place of `{name}`.

A name stays taken until you delete the function that has it, whatever its **Status**. A function
that reads **Failed** still holds its name.

To fix it, do one of these:

- Choose a different name for the new function.
- Delete the function that has the name, then create the new one. Deleting removes that function
  and its stored code for good. See [Delete a function](/myaccount/functions/how-to/delete-a-function/).

## Invalid ZIP structure. Expected single root directory

When you upload a ZIP in **Create Function**, MyAccount checks it before its files open in the
editor. A ZIP with more than one folder at its top level gets "Invalid ZIP structure. Expected
single root directory".

Put all your files in one root directory, then zip that directory and upload it again. See
[Upload code as a ZIP](/myaccount/functions/how-to/upload-code-as-a-zip/#prepare-the-zip).

## Missing required files in root: {files}

Your ZIP does not have every file your runtime needs. In place of `{files}`, MyAccount names the
files it could not find. For example, on a Python runtime, "Missing required files in root:
requirements.txt" means the ZIP has no requirements.txt beside func.py.

Every runtime needs its code file and its requirements file. Python needs func.py and
requirements.txt, and Node.js (Http) needs index.mjs and package.json. For every runtime, see
[Language runtimes](/myaccount/functions/concepts/runtimes-and-hardware/#language-runtimes).

To fix it:

1. Put the named files in the ZIP's root directory, the folder at the top of the ZIP that holds
   your code. Name each file exactly as the message shows it.
2. Zip that directory again, and upload the new ZIP.

## The uploaded ZIP file is too large. Maximum allowed size is 50MB.

The upload check shows "The uploaded ZIP file is too large. Maximum allowed size is 50MB." for a
ZIP over 50 MB.

Make the ZIP 50 MB or smaller. Leave out files the function does not need to run. Its contents
can be up to 200 MB once extracted. See
[Upload code as a ZIP](/myaccount/functions/how-to/upload-code-as-a-zip/).

## File must be a ZIP archive

The upload check shows "File must be a ZIP archive" or "File is not a valid ZIP archive" when the
file you upload is not a ZIP.

Zip the root directory of your code again, then upload the new ZIP. See
[Upload code as a ZIP](/myaccount/functions/how-to/upload-code-as-a-zip/#prepare-the-zip).

## Error: Function is in failed state

A function whose **Status** reads **Failed** did not deploy. Open the function's page and read
its **Build Logs** tab. It shows the build output. The **Logs** tab below the Functions list also
combines the function's runtime logs with its build logs.

Check that the requirements or package file lists every dependency your code needs, with the
right versions. Check that you set the environment variables your code needs, and that the code
reads them by the keys you set. See
[Use environment variables](/myaccount/functions/how-to/use-environment-variables/).

To fix the function, change its code on the function's page and click **Save** to rebuild and
redeploy. On a failed function, **Save** becomes available once you change something. See
[Edit a function](/myaccount/functions/how-to/edit-a-function/).

## Generated ZIP exceeds the 50MB limit.

When you click **Create** or **Save**, MyAccount packs the code from the editor into a ZIP. If that
ZIP is over 50 MB, the save stops at "Generated ZIP exceeds the 50MB limit." The function is then
not created or saved.

Make the code smaller so the ZIP it packs stays under 50 MB. For the other message the editor can
show, see
[Failed to prepare function files](#failed-to-prepare-function-files-please-review-the-code-and-try-again).

## Failed to prepare function files. Please review the code and try again.

When you click **Create** or **Save**, MyAccount packs the code from the editor into a ZIP. It
says "Failed to prepare function files. Please review the code and try again." when it could not
make that ZIP at all. The function is not created or saved.

Review the code, then click **Create** or **Save** again. You can also upload your code as a ZIP
instead. See [Upload code as a ZIP](/myaccount/functions/how-to/upload-code-as-a-zip/). For code
that is too large, see
[Generated ZIP exceeds the 50MB limit](#generated-zip-exceeds-the-50mb-limit).

## The function provided no response

When a function gives no response, you see "The function provided no response. This may be due to
exceeding timeout or memory limits. Please review your configuration settings and try again." The
message appears in **Output** when you call the function with **Post Request**.

Check the function's **Timeout (sec)** and **Memory** in **System Configuration**. Raise
**Timeout (sec)** or **Memory**, or make the code faster. See
[Edit a function](/myaccount/functions/how-to/edit-a-function/) and
[The function times out](#the-function-times-out).

## The request is refused with 413 Payload Too Large or 415 Unsupported Media Type

In the Python and Node.js HTTP runtimes, a `413 Payload Too Large` means the request body is
larger than the function's configured body limit. The default limit is 10 MB. To accept larger
bodies, raise the limit, up to 1000 MB, in the function's optional init function. The init
function sets CORS and body handling. See
[Change CORS and body limits with the init function](/myaccount/functions/concepts/requests-and-responses/#change-cors-and-body-limits-with-the-init-function).

In the same runtimes, a `415 Unsupported Media Type` means the request's content type is not
allowed. By default only JSON bodies are accepted. To accept another content type, allow it in
the init function.

In the FastAPI, Flask, and Express runtimes, your app decides what it accepts, and the init
function does not apply. See
[FastAPI, Flask, and Express runtimes](/myaccount/functions/concepts/requests-and-responses/#fastapi-flask-and-express-runtimes).

## The function returns a 500 or 503

If the handler throws, the platform returns `500`, or `503` for an out-of-memory error. A handler
that returns the wrong shape also gets `500`. The caller sees a generic error, never the handler's
error text. A `500` can also be one your own code returns.

Read the **Logs** tab to see what the handler logged, and fix the code. If the function runs out
of memory, raise its **Memory** in **System Configuration**. See
[View logs and monitoring](/myaccount/functions/how-to/view-logs-and-monitoring/) and
[Edit a function](/myaccount/functions/how-to/edit-a-function/).

## The function times out

A function that runs past its **Timeout (sec)** is stopped. The timeout is from 1 to 600 seconds
and defaults to 15 seconds. A caller, such as curl or your application, then gets HTTP 504 with
the text "activator request timeout". In MyAccount, a call made with **Post Request** that gets
no response shows "The function provided no response." in **Output**.

Check **Timeout (sec)** in the function's **System Configuration**. Raise it or **Memory**, or
make the code faster. See
[Edit a function](/myaccount/functions/how-to/edit-a-function/) and
[The function provided no response](#the-function-provided-no-response).

## You cannot deactivate the FaaS plan while functions are active

You see "You cannot deactivate the FaaS plan while functions are active. Please delete all functions
before proceeding with deactivation." when you try to deactivate with functions still present.

Delete every function, then deactivate. See
[Delete a function](/myaccount/functions/how-to/delete-a-function/) and
[Deactivate Functions](/myaccount/functions/how-to/deactivate-functions/).

## Contact support

If none of this helps, write to cloud-platform@e2enetworks.com. Include the function's name, the
time it happened, and the exact error text you saw.
