PHLO UUID not found about plivo-node HOT 3 CLOSED

Another thing that might be happening is after few modifications to the PHLO and reading at the error responses it seems to be that the failed state has to be set to another node regardless. In my scenario I don't want to act on a failed state, hence I don't think it needs to be set to another node.

from plivo-node.

This is also happening via a regular fetch with proper Authorization using the same parameters and payload. It seems that the bug is within the API itself and not the Plivo node library.

from plivo-node.

@antoniobologna Thank you for the feedback!
I tested the aforementioned API and found it to be very useful. I believe one of the reasons for the failure is that the destination or from number you're trying to pass as input is either invalid or destination country is blocked (which can be unblocked from your dashboard if it exists). Otherwise, feel free to contact our support team to better troubleshoot this error.

from plivo-node.