diff --git a/menu/navigation.json b/menu/navigation.json
index 5eb5a53088..281ddd7a04 100644
--- a/menu/navigation.json
+++ b/menu/navigation.json
@@ -3703,16 +3703,6 @@
"label": "API/CLI",
"slug": "api-cli"
},
- {
- "items": [
- {
- "label": "Common errors",
- "slug": "common-errors"
- }
- ],
- "label": "Troubleshooting",
- "slug": "troubleshooting"
- },
{
"items": [
{
@@ -3766,6 +3756,40 @@
],
"label": "Additional Content",
"slug": "reference-content"
+ },
+ {
+ "items": [
+ {
+ "label": "Unable to create a namespace",
+ "slug": "cannot-create-namespace"
+ },
+ {
+ "label": "I cannot inject secrets or variables in my job",
+ "slug": "cannot-inject-secret-variable"
+ },
+ {
+ "label": "My function is in an error state",
+ "slug": "function-in-error-state"
+ },
+ {
+ "label": "My function stopped working after a redeploy",
+ "slug": "function-stopped-after-redeploy"
+ },
+ {
+ "label": "Handler not found",
+ "slug": "handler-not-found"
+ },
+ {
+ "label": "I am experiencing timeout errors",
+ "slug": "timeout-error"
+ },
+ {
+ "label": "My function fails after too many retries",
+ "slug": "too-many-retries"
+ }
+ ],
+ "label": "Troubleshooting",
+ "slug": "troubleshooting"
}
],
"label": "Functions",
@@ -3861,16 +3885,6 @@
"label": "API/CLI",
"slug": "api-cli"
},
- {
- "items": [
- {
- "label": "Common errors",
- "slug": "common-errors"
- }
- ],
- "label": "Troubleshooting",
- "slug": "troubleshooting"
- },
{
"items": [
{
@@ -3908,6 +3922,32 @@
],
"label": "Additional Content",
"slug": "reference-content"
+ },
+ {
+ "items": [
+ {
+ "label": "I cannot create a namespace",
+ "slug": "cannot-create-namespace"
+ },
+ {
+ "label": "I cannot deploy my image",
+ "slug": "cannot-deploy-image"
+ },
+ {
+ "label": "I cannot inject secrets or variables in my job",
+ "slug": "cannot-inject-secret-variable"
+ },
+ {
+ "label": "I cannot retrieve external images",
+ "slug": "cannot-retrieve-external-image"
+ },
+ {
+ "label": "My container stopped working after a redeploy",
+ "slug": "container-stopped-after-redeploy"
+ }
+ ],
+ "label": "Troubleshooting",
+ "slug": "troubleshooting"
}
],
"label": "Containers",
@@ -3965,16 +4005,6 @@
"label": "How to",
"slug": "how-to"
},
- {
- "items": [
- {
- "label": "Common errors",
- "slug": "common-errors"
- }
- ],
- "label": "Troubleshooting",
- "slug": "troubleshooting"
- },
{
"items": [
{
@@ -4006,6 +4036,24 @@
],
"label": "Additional Content",
"slug": "reference-content"
+ },
+ {
+ "items": [
+ {
+ "label": "My job is in an error state",
+ "slug": "job-in-error-state"
+ },
+ {
+ "label": "I cannot inject secrets or variables in my job",
+ "slug": "cannot-inject-secret-variable"
+ },
+ {
+ "label": "I cannot retrieve external images",
+ "slug": "cannot-retrieve-external-image"
+ }
+ ],
+ "label": "Troubleshooting",
+ "slug": "troubleshooting"
}
],
"label": "Jobs",
diff --git a/serverless/containers/troubleshooting/cannot-create-namespace.mdx b/serverless/containers/troubleshooting/cannot-create-namespace.mdx
new file mode 100644
index 0000000000..cfd5a7c025
--- /dev/null
+++ b/serverless/containers/troubleshooting/cannot-create-namespace.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: I am unable to create a Serverless Containers namespace
+ description: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Containers.
+content:
+ h1: I am unable to create a Serverless Containers namespace
+ paragraph: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Containers.
+tags: serverless Containers troubleshooting issue error namespace creation unable
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+I cannot create a Serverless Containers namespace.
+
+### Cause
+
+This issue can happen for the following reasons:
+
+- You have created too many Serverless Containers namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers).
+
+- You have created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry).
+
+### Possible solutions
+
+Make sure that you have not exceeded the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-namespaces-list-all-your-namespaces).
\ No newline at end of file
diff --git a/serverless/containers/troubleshooting/cannot-deploy-image.mdx b/serverless/containers/troubleshooting/cannot-deploy-image.mdx
new file mode 100644
index 0000000000..cb0ba6e576
--- /dev/null
+++ b/serverless/containers/troubleshooting/cannot-deploy-image.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: I am unable to deploy my image
+ description: Troubleshoot errors encountered while deploying images with Scaleway Serverless Containers.
+content:
+ h1: I am unable to deploy my image
+ paragraph: Troubleshoot errors encountered while deploying images with Scaleway Serverless Containers.
+tags: serverless containers troubleshooting issue error message deploy image failed
+dates:
+ validation: 2024-11-07
+ posted: 2024-11-07
+categories:
+ - serveless
+---
+
+## Problem
+
+I am unable to deploy my image using Serverless Containers.
+
+## Possible solutions
+
+- Make sure the container is listening on the specified PORT for HTTP requests (or use variable `$PORT`).
+
+- Make sure the container is bound to `0.0.0.0`.
+
+- Containers cannot start due to insufficient provisioned resources. Update your container's resources by provisioning more memory and more vCPU.
+
+- Make sure you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/containers/reference-content/containers-limitations/#Architecture) documentation for more information.
+
+- Make sure your deployment does not exceed the limitations of [Serverless Containers](/serverless/containers/reference-content/containers-limitations/).
+
+
+ Run the [`docker inspect`](https://docs.docker.com/engine/reference/commandline/inspect/) command to get detailed information on your image:
+ ```
+ docker inspect myimage
+ ```
+
\ No newline at end of file
diff --git a/serverless/containers/troubleshooting/cannot-inject-secret-variable.mdx b/serverless/containers/troubleshooting/cannot-inject-secret-variable.mdx
new file mode 100644
index 0000000000..0b5a7e5e43
--- /dev/null
+++ b/serverless/containers/troubleshooting/cannot-inject-secret-variable.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: My secrets and variables are not injected properly in my container
+ description: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Containers.
+content:
+ h1: My secrets and variables are not injected properly in my container
+ paragraph: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Containers.
+tags: serverless containers troubleshooting issue error image env var environment variables secrets secret manager
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+My environment variables and secrets are not properly injected in my Serverless Container.
+
+## Cause
+
+Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly.
+
+```
+"hello
+world
+.
+"
+```
+
+### Solution
+
+To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`.
diff --git a/serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx b/serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx
new file mode 100644
index 0000000000..3dc80f6cad
--- /dev/null
+++ b/serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx
@@ -0,0 +1,28 @@
+---
+meta:
+ title: I am unable to retrieve an external image for my container
+ description: Troubleshoot errors while retrieving external images while using Scaleway Serverless Containers.
+content:
+ h1: I am unable to retrieve an external image for my container
+ paragraph: Troubleshoot errors while retrieving external images while using Scaleway Serverless Containers.
+tags: serverless containers troubleshooting issue error image retrieve external public registry
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+I am experiencing issues when retrieving an image stored in an external container registry.
+
+## Cause
+
+Serverless products support external public registries (such as [Docker Hub](https://hub.docker.com/)), but we do not recommend using them due to uncontrolled rate limiting, which can lead to failures when starting resources, unexpected usage conditions, and pricing changes.
+
+## Solution
+
+We recommend using the [Scaleway Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Containers at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry).
+
+Refer to the [dedicated documentation](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/) for more information on how to migrate images to the Scaleway Container Registry.
diff --git a/serverless/containers/troubleshooting/common-errors.mdx b/serverless/containers/troubleshooting/common-errors.mdx
deleted file mode 100644
index d2fe6930cc..0000000000
--- a/serverless/containers/troubleshooting/common-errors.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
----
-meta:
- title: Common errors encountered while using Serverless Containers
- description: Troubleshoot common errors in Scaleway Serverless Containers.
-content:
- h1: Common errors encountered while using Serverless Containers
- paragraph: Troubleshoot common errors in Scaleway Serverless Containers.
-tags: serverless containers troubleshooting issue error message
-dates:
- validation: 2024-09-02
- posted: 2023-08-24
-categories:
- - serveless
----
-
-## Unable to deploy the image
-
-### Possible solutions
-
-- Make sure the container is listening on the specified PORT for HTTP requests (or use variable `$PORT`).
-
-- Make sure the container is bound to `0.0.0.0`.
-
-- Containers cannot start due to insufficient provisioned resources. Update your container's resources by provisioning more memory and more vCPU.
-
-- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported. See [Architecture](/serverless/containers/reference-content/containers-limitations/#Architecture) documentation.
-
-- Make sure your deployment does not exceed the limitations of [Serverless Containers](/serverless/containers/reference-content/containers-limitations/).
-
-
- Run the [`docker inspect`](https://docs.docker.com/engine/reference/commandline/inspect/) command to get detailed information on your image:
- ```
- docker inspect myimage
- ```
-
-
-## Failed to create a namespace
-
-### Cause
-
-This issue can happen for the following reasons:
-
-- You created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers)
-- You created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry)
-
-### Possible solutions
-
-Make sure that you did not exceed the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-namespaces-list-all-your-namespaces).
-
-## Container stopped working several hours after a redeploy
-
-### Cause
-
-The new deploy failed, and the [fallback mechanism has been triggered](/serverless/containers/reference-content/containers-limitations/#versioning-and-rollback).
-
-### Possible solution
-
-Identify the element that caused the deployment to fail, fix the error, and deploy the container again.
-
-## Issues when retrieving an external image
-
-### Cause
-
-Serverless products support external public registries (such as [Docker Hub](https://hub.docker.com/)), but we do not recommend using them due to uncontrolled rate limiting, which can lead to failures when starting resources, unexpected usage conditions, and pricing changes.
-
-### Solution
-
-We recommend using [Scaleway's Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Jobs at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry).
-
-## My environment variable or secret is not properly injected in my container
-
-### Cause
-
-Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly.
-
-```
-"hello
-world
-.
-"
-```
-
-### Solution
-
-To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`.
\ No newline at end of file
diff --git a/serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx b/serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx
new file mode 100644
index 0000000000..ac8b4da469
--- /dev/null
+++ b/serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx
@@ -0,0 +1,26 @@
+---
+meta:
+ title: My container stopped working after a redeploy
+ description: Troubleshoot issues with Scaleway Serverless Containers not working properly following a redeploy.
+content:
+ h1: My container stopped working after a redeploy
+ paragraph: Troubleshoot issues with Scaleway Serverless Containers not working properly following a redeploy.
+tags: serverless containers troubleshooting issue error state failed fail redeploy
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+My Serverless Container stopped working (up to several hours) after a redeploy.
+
+## Cause
+
+The new deploy failed, and the [fallback mechanism has been triggered](/serverless/containers/reference-content/containers-limitations/#versioning-and-rollback).
+
+## Possible solution
+
+Identify the element that caused the deployment to fail, fix the error, and deploy the container again.
\ No newline at end of file
diff --git a/serverless/functions/troubleshooting/cannot-create-namespace.mdx b/serverless/functions/troubleshooting/cannot-create-namespace.mdx
new file mode 100644
index 0000000000..55760c1959
--- /dev/null
+++ b/serverless/functions/troubleshooting/cannot-create-namespace.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: I am unable to create a Serverless Functions namespace
+ description: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Functions.
+content:
+ h1: I am unable to create a Serverless Functions namespace
+ paragraph: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Functions.
+tags: serverless functions troubleshooting issue error namespace creation unable
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+I cannot create a Serverless Functions namespace.
+
+### Cause
+
+This issue can happen for the following reasons:
+
+- You have created too many Serverless Functions namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-functions).
+
+- You have created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry).
+
+### Possible solutions
+
+Make sure that you have not exceeded the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-namespaces-list-all-your-namespaces).
\ No newline at end of file
diff --git a/serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx b/serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx
new file mode 100644
index 0000000000..63f0884702
--- /dev/null
+++ b/serverless/functions/troubleshooting/cannot-inject-secret-variable.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: My secrets and variables are not injected properly in my function
+ description: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Functions.
+content:
+ h1: My secrets and variables are not injected properly in my function
+ paragraph: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Functions.
+tags: serverless functions troubleshooting issue error env var environment variables secrets secret manager
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+My environment variable or secret is not properly injected in my function during its execution.
+
+### Cause
+
+Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly.
+
+```
+"hello
+world
+.
+"
+```
+
+### Solution
+
+To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`.
\ No newline at end of file
diff --git a/serverless/functions/troubleshooting/common-errors.mdx b/serverless/functions/troubleshooting/common-errors.mdx
deleted file mode 100644
index f72bfef40a..0000000000
--- a/serverless/functions/troubleshooting/common-errors.mdx
+++ /dev/null
@@ -1,127 +0,0 @@
----
-meta:
- title: Common errors encountered while using Serverless Functions
- description: Troubleshoot common errors encountered with Scaleway Serverless Functions.
-content:
- h1: Common errors encountered while using Serverless Functions
- paragraph: Troubleshoot common errors encountered with Scaleway Serverless Functions.
-tags: serverless functions troubleshooting issue error message
-dates:
- validation: 2024-05-08
- posted: 2023-08-23
-categories:
- - serveless
----
-
-## Handler not found
-
-### Error Messages
-
- ```
- Function Handler does not exist, check that you provided the right HANDLER parameter …
- ```
-
- Or
-
- ```
- Provided Handler does not exist, or does not export methods properly
- ```
-
-### Cause
-
-The systems cannot find the function which will handle the request. It can be related to an error in your code before your `handle` function.
-
-### Possible solutions
-
-- Make sure to provide the right handler path.
-
-- If you used a zip file, make sure the dependencies are present in your [zip package](/serverless/functions/how-to/package-function-dependencies-in-zip/).
-
-- If you used the Serverless framework, ensure the `.serverless` directory created with `serverless package` contains your zip file.
-
-- Make sure that the dependencies folders (`node_modules` or `package` in Python) are in package/include.
-
-- Serverless Functions rely on Alpine Linux, therefore, some C-based libraries (`pandas`, `tensorflow`, `numpy`) will not work. Refer to the official documentation to safely add these libraries to your package.
-
-## Too Many Retries
-
-### Error messages
-
-```
-Too many retries, sub-runtime server did not come up in 10ms seconds
-```
-
-### Cause
-
-This error is returned by the runtime when it cannot process the request. It has several different origins.
-
-### Possible solutions
-
-- Make sure that you only imported the required dependencies and not the complete libraries.
-
-- Avoid performing too many initialization operations.
-
-- Update your function's resources by provisioning more memory and more vCPU.
-
-## Function in error state
-
-### Cause
-
-This error is returned when the function cannot start due to insufficient provisioned resources.
-
-### Possible solutions
-
-Update your function's resources by provisioning more memory and more vCPU.
-
-## Timeout error
-
-### Cause
-
-Timeout happens when your function can’t return a results in the defined amount of time.
-
-### Possible solutions
-
-- Increase the Timeout parameter in the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-functions-update-an-existing-function).
-
-- Update your function's resources by provisioning more memory and more vCPU.
-
-## Failed to create a namespace
-
-### Cause
-
-This issue can happen for the following reasons:
-
-- You created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-functions).
-
-- You created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry).
-
-### Possible solutions
-
-Make sure that you did not exceed the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-namespaces-list-all-your-namespaces).
-
-## Function stopped working several hours after a redeploy
-
-### Cause
-
-The new deploy failed, and the [fallback mechanism has been triggered](/serverless/functions/reference-content/functions-limitations/#versioning-and-rollback).
-
-### Possible solution
-
-Identify the element that caused the deployment to fail, fix the error, and deploy the function again.
-
-## My environment variable or secret is not properly injected in my function
-
-### Cause
-
-Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly.
-
-```
-"hello
-world
-.
-"
-```
-
-### Solution
-
-To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`.
diff --git a/serverless/functions/troubleshooting/function-in-error-state.mdx b/serverless/functions/troubleshooting/function-in-error-state.mdx
new file mode 100644
index 0000000000..773de5a27d
--- /dev/null
+++ b/serverless/functions/troubleshooting/function-in-error-state.mdx
@@ -0,0 +1,26 @@
+---
+meta:
+ title: My function is in an error state
+ description: Troubleshoot issues with Scaleway Serverless Functions being in an error state.
+content:
+ h1: My function is in an error state
+ paragraph: Troubleshoot issues with Scaleway Serverless Functions being in an error state.
+tags: serverless functions troubleshooting issue error state failed fail
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+My Serverless Function is in an error state following its execution.
+
+## Cause
+
+This error is returned when the function cannot start due to insufficient provisioned resources.
+
+## Possible solution
+
+Update your function's resources by provisioning more memory and more vCPU.
\ No newline at end of file
diff --git a/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx b/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx
new file mode 100644
index 0000000000..bc29517c5c
--- /dev/null
+++ b/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx
@@ -0,0 +1,26 @@
+---
+meta:
+ title: My function stopped working after a redeploy
+ description: Troubleshoot issues with Scaleway Serverless Functions not working properly following a redeploy.
+content:
+ h1: My function stopped working after a redeploy
+ paragraph: Troubleshoot issues with Scaleway Serverless Functions not working properly following a redeploy.
+tags: serverless functions troubleshooting issue error state failed fail redeploy
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+My Serverless Function stopped working (up to several hours) after a redeploy.
+
+## Cause
+
+The new deploy failed, and the [fallback mechanism has been triggered](/serverless/functions/reference-content/functions-limitations/#versioning-and-rollback).
+
+## Possible solution
+
+Identify the element that caused the deployment to fail, fix the error, and deploy the function again.
\ No newline at end of file
diff --git a/serverless/functions/troubleshooting/handler-not-found.mdx b/serverless/functions/troubleshooting/handler-not-found.mdx
new file mode 100644
index 0000000000..5a85404b2e
--- /dev/null
+++ b/serverless/functions/troubleshooting/handler-not-found.mdx
@@ -0,0 +1,44 @@
+---
+meta:
+ title: Unable to find the function handler
+ description: Troubleshoot problems with finding the handler when using Scaleway Serverless Functions.
+content:
+ h1: Unable to find the function handler
+ paragraph: Troubleshoot problems with finding the handler when using Scaleway Serverless Functions.
+tags: serverless functions troubleshooting issue error function handler execution run cannot find
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+My serverless Function is unable to find the handler during its execution, and displays an error message similar to the following:
+
+```
+Function Handler does not exist, check that you provided the right HANDLER parameter …
+```
+
+Or
+
+```
+Provided Handler does not exist, or does not export methods properly
+```
+
+## Cause
+
+The systems cannot find the function that should handle the request. It may be related to an error in your code before your `handle` function.
+
+## Possible solutions
+
+- Make sure to provide the right handler path.
+
+- If you have used a zip file, make sure the dependencies are present in your [zip package](/serverless/functions/how-to/package-function-dependencies-in-zip/).
+
+- If you have used the Serverless framework, ensure the `.serverless` directory created with `serverless package` contains your zip file.
+
+- Make sure that the dependencies folders (`node_modules` or `package` in Python) are in package/include.
+
+- Serverless Functions rely on Alpine Linux. Therefore, some C-based libraries (`pandas`, `tensorflow`, `numpy`) will not work. Refer to the official documentation to safely add these libraries to your package.
\ No newline at end of file
diff --git a/serverless/functions/troubleshooting/timeout-error.mdx b/serverless/functions/troubleshooting/timeout-error.mdx
new file mode 100644
index 0000000000..50dac1975c
--- /dev/null
+++ b/serverless/functions/troubleshooting/timeout-error.mdx
@@ -0,0 +1,28 @@
+---
+meta:
+ title: I am experiencing timeout errors
+ description: Troubleshoot timeout errors when using Scaleway Serverless Functions.
+content:
+ h1: I am experiencing timeout errors
+ paragraph: Troubleshoot timeout errors when using Scaleway Serverless Functions.
+tags: serverless functions troubleshooting issue error function timeout
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+I am experiencing timeout errors when using Scaleway Serverless Functions.
+
+### Cause
+
+Timeout happens when your function cannot return any result in the defined amount of time.
+
+### Possible solutions
+
+- Increase the Timeout parameter in the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-functions-update-an-existing-function).
+
+- Update your function's resources by provisioning more memory and more vCPU.
\ No newline at end of file
diff --git a/serverless/functions/troubleshooting/too-many-retries.mdx b/serverless/functions/troubleshooting/too-many-retries.mdx
new file mode 100644
index 0000000000..bf7191b130
--- /dev/null
+++ b/serverless/functions/troubleshooting/too-many-retries.mdx
@@ -0,0 +1,34 @@
+---
+meta:
+ title: My function fails after trying too many times
+ description: Troubleshoot problems with functions trying too many times before failing.
+content:
+ h1: My function fails after trying too many times
+ paragraph: Troubleshoot problems with functions trying too many times before failing.
+tags: serverless functions troubleshooting issue error function retries retry failure
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+My function fails, and the following message displays:
+
+```
+Too many retries, sub-runtime server did not come up in 10ms seconds
+```
+
+## Cause
+
+This error is returned by the runtime when it cannot process the request. It has several different origins.
+
+## Possible solutions
+
+- Make sure that you have only imported the required dependencies and not the complete libraries.
+
+- Avoid performing too many initialization operations.
+
+- Update your function's resources by provisioning more memory and more vCPU.
\ No newline at end of file
diff --git a/serverless/jobs/troubleshooting/cannot-inject-secret-variable.mdx b/serverless/jobs/troubleshooting/cannot-inject-secret-variable.mdx
new file mode 100644
index 0000000000..f60610fd35
--- /dev/null
+++ b/serverless/jobs/troubleshooting/cannot-inject-secret-variable.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: My secrets and variables are not injected properly in my job
+ description: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Jobs.
+content:
+ h1: My secrets and variables are not injected properly in my job
+ paragraph: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Jobs.
+tags: serverless jobs troubleshooting issue error image env var environment variables secrets secret manager
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+My environment variables and secrets are not properly injected during my job runs.
+
+## Cause
+
+Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly.
+
+```
+"hello
+world
+.
+"
+```
+
+### Solution
+
+To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`.
diff --git a/serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx b/serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx
new file mode 100644
index 0000000000..cc53cc5394
--- /dev/null
+++ b/serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx
@@ -0,0 +1,28 @@
+---
+meta:
+ title: I am unable to retrieve an external image for my job
+ description: Troubleshoot errors while retrieving external images while using Scaleway Serverless Jobs.
+content:
+ h1: I am unable to retrieve an external image for my job
+ paragraph: Troubleshoot errors while retrieving external images while using Scaleway Serverless Jobs.
+tags: serverless jobs troubleshooting issue error image retrieve external public registry
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+I am experiencing issues when retrieving an image stored in an external container registry.
+
+## Cause
+
+Serverless products support external public registries (such as [Docker Hub](https://hub.docker.com/)), but we do not recommend using them due to uncontrolled rate limiting, which can lead to failures when starting resources, unexpected usage conditions, and pricing changes.
+
+## Solution
+
+We recommend using the [Scaleway Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Jobs at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry).
+
+Refer to the [dedicated documentation](/serverless/jobs/api-cli/migrate-external-image-to-scaleway-registry/) for more information on how to migrate images to the Scaleway Container Registry.
diff --git a/serverless/jobs/troubleshooting/common-errors.mdx b/serverless/jobs/troubleshooting/common-errors.mdx
deleted file mode 100644
index a6d923a3ce..0000000000
--- a/serverless/jobs/troubleshooting/common-errors.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-meta:
- title: Common errors encountered while using Serverless Jobs
- description: Troubleshoot common errors in Scaleway Serverless Jobs.
-content:
- h1: Common errors encountered while using Serverless Jobs
- paragraph: Troubleshoot common errors in Scaleway Serverless Jobs.
-tags: serverless jobs troubleshooting issue error message
-dates:
- validation: 2024-10-03
- posted: 2024-03-28
-categories:
- - serverless
----
-
-## Job run is in an error state
-
-### Possible solutions
-
-- Make sure you built your image for an `amd64` architecture, as `arm64` is not supported. See [Architecture](/serverless/jobs/reference-content/jobs-limitations/#Architecture) documentation.
-
-- Make sure your deployment does not exceed the limitations of [Serverless Jobs](/serverless/jobs/reference-content/jobs-limitations/).
-
-## Issues when retrieving an external image
-
-### Cause
-
-Serverless products support external public registries (such as [Docker Hub](https://hub.docker.com/)), but we do not recommend using them due to uncontrolled rate limiting, which can lead to failures when starting resources, unexpected usage conditions, and pricing changes.
-
-### Solution
-
-We recommend using [Scaleway's Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Jobs at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry).
-
-## My environment variable or secret is not properly injected in my job
-
-### Cause
-
-Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly.
-
-```
-"hello
-world
-.
-"
-```
-
-### Solution
-
-To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`.
\ No newline at end of file
diff --git a/serverless/jobs/troubleshooting/job-in-error-state.mdx b/serverless/jobs/troubleshooting/job-in-error-state.mdx
new file mode 100644
index 0000000000..90614acdcb
--- /dev/null
+++ b/serverless/jobs/troubleshooting/job-in-error-state.mdx
@@ -0,0 +1,24 @@
+---
+meta:
+ title: My Job run is in an error state
+ description: Troubleshoot error states for your Scaleway Serverless Jobs.
+content:
+ h1: My Job run is in an error state
+ paragraph: Troubleshoot error states for your Scaleway Serverless Jobs.
+tags: serverless jobs troubleshooting issue error state message
+dates:
+ validation: 2024-11-06
+ posted: 2024-11-06
+categories:
+ - serverless
+---
+
+## Problem
+
+My job run is in an error state.
+
+## Possible solutions
+
+- Make sure that you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/jobs/reference-content/jobs-limitations/#Architecture) documentation for more information.
+
+- Make sure that your deployment does not exceed the limitations of [Serverless Jobs](/serverless/jobs/reference-content/jobs-limitations/).
\ No newline at end of file