This page provides an overview of all the errors that the platform can produce. It will provide a brief explanation of the error and potential solutions.

Function Invocation

During the invocation of a function, you might be returned one of the following error codes. Those should allow you to get a better understanding of what has happened. Please be aware that there might be situations where the platform is not able to produce those errors and returns a generic error.

• 401/403 — Authentication failed: There are issues with the provided token. Either it expired, or the user does not have the correct permissions.
• 404 — Not Found: This error is returned if the function is not deployed (not in a productive state) or if the function does not exist. (Code: com.liveperson.faas.function.not-found)
• 429 - Rate Limit Exceeded: The function you invoked has received too many requests in a short time, and we started to throttle the requests. This issue can also occur when there are too many "inflight" requests, causing the maximum amount of instances to be used up. For more details on instance limits, please refer to the limitations page.
• 901 — Invocation failed: This error is raised when there is an issue during the function's invocation. The response will include specific error codes to help identify the source of the problem. Common causes include:
  • Function Threw Error: The function logic explicitly returned an error.
    • Codes: com.customer.faas.function.threw-error, com.liveperson.faas.handler.custom-failure
  • JS Runtime Exception: A runtime error occurred, such as accessing a method on undefined or null.
    • Codes: com.customer.faas.function.js-runtime-error, com.liveperson.faas.handler.runtime-exception
  • Execution Window Exceeded: The function took longer to execute than the allowed timeout.
    • Codes: com.customer.faas.function.execution-exceeded, com.liveperson.faas.handler.executiontime-exceeded

  The error is only raised if you are leveraging one of our clients for external invocation.