I’ve been battling with a (Python) Function deployed inside the App Platform, failing with a (pretty useless) “There was an error processing your request.” message.
Turns out that my function was just taking more than 3000ms to execute, which is the default timeout for a Function.
You can change the timeout in package.yml, by adding this to your Action:
actions:
- name: <your Function's name>
limits:
timeout: 30000 # The new timeout, in milliseconds
BUT, I think DigitalOcean should make any web Function that times out return an HTTP 408 Request Timeout, which would be more precise, and would give developers much more useful information to act upon (and save us a lot of frustration to debug).
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hey Dancecard Admin,
Thank you for sharing this suggestion! I’ll make sure to forward your feedback to the appropriate team internally.
In the meantime, feel free to post this as an idea on the ideas board here:
- Bobby.