Common Issues
Having questions? Join our Discord community and let's talk.
We welcome contributions to this page - if you contributed an issue resolution that appears in this page, we'll make sure everybody knows who you are - and we'll send you some complimentary Cloudonix Swag.
Make RuntimeError [404]
When using Operational Modules (eg. Get Active Sessions or
Make Call and Do Something Smart) - a 404 error may be reported
back from Cloudonix.
If this happens, it means that you've used your personal Customer API Key.
The resulting 404 error is caused by using the wrong API Key type. To use the Make applicaion, you are required to use a Domain API Key.
Any other Key type will result with either a 404 or 403 error.
Incomplete Scenario
A common mistake is to forget the Voice Application Response module at the end of your scenario. This module serves is similar to a "Webhook Response" in Make, however, will allow you to continue execution the scenario, after the response has been provided to Cloudonix.
Improper Execution Order
Normally, when modules are executed on Make, they are executed in order. However, when your Voice Application Response is created, you must pay attention to the order of the module output you provide to it.
For example:
In the above example, you can see that module number 461 is executed after 388 and 389, however, when forming the output response, module 461 is provided first. Pay attention to the order of your final response, as it will affect your final Cloudonix call-flow execution.