400 error bad number
# support
l
I'm getting a few 400 errors that are due to numbers being disconnected. This is throwing off Make.com automations. What's the best practice for catching those errors and handling better? 400 error is just 'bad request' - I'd like to be able to identify this particular type of bad request (an offline phone number), differently to general bad requests.
v
Thanks for your question! Based on the information available, I don't have specific details on how to distinguish 400 errors caused by disconnected numbers from other types of bad requests, or best practices for handling these in Make.com automations. If you have access to more detailed error messages or logs, you might be able to implement custom logic to differentiate these cases, but unfortunately, I don't have documentation or examples to share on this topic.
v
Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!