Error Calling SendOutboundMessage function

[davidbotts-netizen]

Good afternoon. I have this plugin installed in a localhost dev environment. I have an error that comes up each time I try to send an outbound message (See image).
We have verified that the function code is working. We can trigger the command with a separate test.js file and CURl commands, and messages deliver. However, when trying to use the UI, we continue to get this error. I have confirmed the .env file is populated with the domain of the live function that is verified to be working.
My backend developer suggested this seems to be an issue with something on the front end not handling the function correctly. Is there a suggestion for what step of install I may be missing?

[dahamilton-twilio]

Hi David - To debug this it would be useful to check the network tab in your browsers developers tools to confirm if the UI is sending the request to your deployed function or to your locally running functions. If the function is being invoked the try/catch handing in the function might also be returning a clue.

if you determine the function is being invoked you can also check the logs:
https://www.twilio.com/docs/serverless/functions-assets/functions/debugging

Let me know what you are seeing in the network tab if you need any additional help.

[davidbotts-netizen]

Good call. So, right now it's not showing. In the repo, I did a quick command to see if the UI fires, and saw this;

drbotts@iMacPro outbound-cbm % grep -R "sendOutboundMessage" -n src

src/actions/sendOutboundMessage.js:4:const sendOutboundMessage = async (sendOutboundParams) => {
src/actions/sendOutboundMessage.js:25: ${process.env.FLEX_APP_TWILIO_SERVERLESS_DOMAIN}/sendOutboundMessage,
src/actions/sendOutboundMessage.js:44: message: "Error calling sendOutboundMessage function",
src/actions/sendOutboundMessage.js:71: sendOutboundMessage(sendOutboundParams);
src/actions/sendOutboundMessage.js:88: sendOutboundMessage(sendOutboundParams);
src/OutboundMessageCBM.js:6:import "./actions/sendOutboundMessage";
drbotts@iMacPro outbound-cbm %

Still trying to figure this one out.

Of note, on Network, I tried all of these filters. Nothing.
actions/sendOutboundMessage
twil.io
sendOutbound

[davidbotts-netizen]

Of note, this does work. Redacted details

curl -i -X POST https://outbound-messaging-****-dev.twil.io/actions/sendOutboundMessage
--data-urlencode 'to=+MYPHONENUMBER'
--data-urlencode 'body=Hello from CBM'

[dahamilton-twilio]

Hi David - Can you double check the .env file in the root of the plugin folder and just to be sure add a console log in the flex plugin to log out and check process.env.FLEX_APP_TWILIO_SERVERLESS_DOMAIN?

Note that it also expects it to include the protocol (https://)

[davidbotts-netizen]

From what I can see, the URL is pulling corectly. Here is a snapshot of those logs when I added that code, good suggestion. I tried to expand some detail on the errors I'm seeing. I hope this gives you a little more insight.

[dahamilton-twilio]

Hi David - Thanks for sharing the logs.

This shows that xxx.io/sendOutboundMessage is not a valid path and Twilio serverless is returning 404.

The curl command you shared shows that the function is deployed in a different folder (actions) compared to what the plugin is expecting.
xxx.io/actions/sendOutboundMessage)

Moving the function to the root folder or updating the plugin code with the new path should resolve this.

[davidbotts-netizen]

Oh odd. I thought this code was just a replicate from the Repo, so i didn't want to adjust it. What step am I missing then? Because see here, this is the structure. For example, if I just move it to the root folder, there's a compliling error.

[dahamilton-twilio]

Hi David - The Flex UI Plugin code sendOutboundMessage.js file is expected to be in the /src/actions folder.

I think the issue is with the serverless/outbound-messaging/functions/sendOutboundMessage.js file which is the backend function that the plugin makes a http request to. If you check via the twilio console I expect you will find the function has been deployed to serverless/outbound-messaging/functions/actions/sendOutboundMessage.js.

The reason I think this is deployed differently to the default plugin is based on the url you are passing to the curl command.

[dahamilton-twilio]

Hi again David - I looked up your Twilio account SID and checked the content of the
/actions/sendOutboundMessage file in your twilio service and it isn't as simple as the function being deployed in a different directory. The sendOutboundMessage function in your service is very different to the function the plugin is expecting to call:

https://github.com/twilio-professional-services/plugin-outbound-cbm/blob/master/serverless/outbound-messaging/functions/sendOutboundMessage.js

It looks like there is either a misunderstanding on how the UI plugin interacts with the Twilio functions or you are intentionally changing how the backend will work for a use case that the UI plugin wasn't originally designed to support.
From looking at the function it could be that you are just trying to support a single outbound message (using programmable messaging APIs rather than conversations APIs) and are not looking to handle responses or create a task in flex.

[davidbotts-netizen]

Thank you so much for taking the initiative and time to look into this for me. I wanted to respond yesterday, and take the time today, but my corporate tax returns just hit my desk and now I'm tied up with that. I do have a response, and if it's at all possible to message you outside of this thread to work through those last details to get this across the finish line, do please let me know. If not, I'll try to post an update here in 24 hours and explain more of what you are seeing.