Migrating from Functions(Classic) to the new Functions Editor
The Functions Editor is the all-new, redesigned way to experience Twilio Functions.
Functions(Classic) now has its own sub-menu in the Twilio Console, within the Functions product menu.
Advantages of the new editor include:
- The new Functions Editor is built on a separate infrastructure from that of Functions(Classic), and utilizes the latest V2 APIs.
- The ability to access logs live, or via the Logs endpoint at a later date. In Functions(Classic), logs were only available live while in the Console UI.
- Increased reliability and refined user experience.
- Easier organization and separation of your Twilio applications via the use of Services.
How to migrate functions from Functions(Classic) to the new editor
- Create a Service in the new Functions editor to house your application.
- Copy the code from an existing Functions(classic) Function.
- Create a Function of the same name within the Service that you just created, using the Add+ button in new Functions Editor.
- Paste your code into the new Function, and click Save to save the Function.
- Configure any Dependencies for the Service.
- Configure any Environment Variables for the Service.
- Click Deploy all to deploy your Service and all of its Functions (and Assets, if any).
- If you have phone numbers configured to point to your old, Functions(classic) Function, configure the phone numbers to point to the new Function(s) that we just created.
If you have multiple Twilio applications, create a Service for each application. That way, you can group the Functions that belong to a specific application together under one Service.
Assets(Classic) and new Functions Editor are not compatible. You will need to re-upload any Assets(Classic) as Assets in order to work with them in the new editor.
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.