This Twilio product is currently available as a beta release. Some features are not yet implemented and others may be changed before the product is declared as Generally Available. Beta products are not covered by a Twilio SLA.
See this article for more information on beta product support.
There are two possible reasons for why your Function has completed with the error: 'runtime application timed out'.
The most common reason is that your Function has exceeded the 5-second execution time limit. You can determine this by looking at the execution logs on the Function instance page. The last log line after execution will tell you how many milliseconds the Function took to execute. If the processing time is greater than 5,000 milliseconds then your Function was terminated by Twilio.
The other more subtle reason your Function ended with an application timeout is because of an incorrect invocation of
callback(). If the
callback() method is not being called or is unreachable, your Function will continue executing until it reaches the time limit and ultimately fails. A very common mistake is to forget to capture the
catch() rejected state of a
Promise and calling
callback() there as well. The Function Execution documentation provides extensive details on the functionality and usage of the
callback() method. Below are several examples of how to correctly use
callback() to complete execution and emit a response.
The most common reason we have seen that a Function appears not to run is the misuse of
callback(). Your Function invocation terminates as soon as the
callback() is reached. If your request is asynchronous, for example, an API call to a Twilio resource, then the
callback() must be placed inside the success response of the request.
Currently, Functions are event-driven and can only be invoked by HTTP.
During the beta period, we currently have a limit of 100 functions per account.
誰しもが一度は考える「コーディングって難しい」。そんな時は、お問い合わせフォームから質問してください。 または、Stack Overflow でTwilioタグのついた情報から欲しいものを探してみましょう。