Recently, we’ve been receiving reports from users that their scenarios in Make are not working correctly.
After a detailed investigation, we noticed the following behavior: instead of a valid authorization token value, our system receives the string “Cannot assign requested address”.
We suspect this might be happening due to the following possible sequence:
-
Make attempts to perform a request to refresh or retrieve an access token.
-
This request fails due to a network issue (e.g., a temporary DNS failure or connection limit exceeded).
-
As a result, Make substitutes the string “Cannot assign requested address” into the variable that is later used in the Authorization header.
-
SendPulse then receives a header like
Authorization: Bearer Cannot assign requested address(which originates from a low-level TCP/socket error) and responds with 401 Unauthorized.
To further investigate and identify a possible solution, it would be helpful to obtain any relevant logs or to know whether requests to our API are marked in any way — for example, with a custom header.