Reference
1 min read

NO_RESPONSE_FROM_FUNCTION

The application did not respond correctly, this is likely due to an exception being thrown from the function handler.
Table of Contents

The NO_RESPONSE_FROM_FUNCTION error occurs when a function invocation completes without returning a response. This might happen if the function encounters an error that prevents it from responding, or if it fails to generate a response within the allowed execution time.

Potential causes include:

  • A global uncaught exception
  • A global unhandled rejection
  • A deployment that introduced incorrect syntax
502

NO_RESPONSE_FROM_FUNCTION

Bad Gateway

To troubleshoot this error, follow these steps:

  1. Verify return statements: Ensure that the function has the necessary return statements to generate a response
  2. Check the function logs: Open the realtime request logs for the application in a separate tab - this tab must be kept open while reproducing the error
  3. Review realtime logs: Repeat the application behavior that led to the error being thrown and review the realtime request logs where it will now show
    • Use the information contained within the error logs to understand where the function is failing
  4. Use log drains: If you're yet to implement a Log Drain, you can create one to persist errors from Serverless Functions
  5. Check external dependencies: If the function relies on external services or APIs, ensure they are responding in a timely manner
Last updated on February 25, 2024