Common errors and solutions for ApsaraMQ for MQTT API calls.
Error quick reference
| Error | Cause | Solution |
|---|---|---|
API not support | Instance version is too old | Purchase a new instance |
| No message trace (HTTP) | HTTP interface does not support message trace | Send messages through an MQTT SDK |
| Intermittent timeouts | QPS limit exceeded, throttling triggered | Reduce call frequency |
SignatureDoesNotMatch | Authentication failed | Verify your AccessKey ID and AccessKey secret |
Why do I get an "API not support" error when creating a rule?
Your instance version is too old to support rules. Purchase a new instance and create the rule again.
Why don't messages sent over the HTTP interface have a message trace?
The HTTP interface does not support message trace. To view message traces, send messages through an MQTT SDK instead.
For details, see Send a single message to ApsaraMQ for MQTT.
Why do I get intermittent timeout errors when calling the API?
ApsaraMQ for MQTT enforces queries per second (QPS) limits on API calls. When your request rate exceeds the limit, throttling kicks in and causes timeout errors.
To resolve this issue, reduce your API call frequency to stay within the QPS threshold.
For specific QPS thresholds, see QPS limits.
Why do I get a SignatureDoesNotMatch error when calling API operations through the SDK?
This error indicates that authentication failed. Verify that your AccessKey ID and AccessKey secret are correctly specified in your SDK configuration.
For details on obtaining your credentials, see Create an AccessKey pair.