Limits and errors
Bounded requests make results easier to review and protect the connected SolarSENS services.
Request limits
| Query type | Maximum window |
|---|---|
| Daily performance data | 366 days |
| Returned rows | 1,000 |
| Serialized response | 1 MB |
Five-minute performance data is not available today. The interval field on
get_performance still accepts 5min, but the production route rejects a
5min request with INVALID_QUERY. Use daily, the default, for every
request.
If a result is truncated, the response says so. Ask for a smaller date range.
Common errors
| Error | Meaning | What to do |
|---|---|---|
| Authentication required | The Public API rejected the signed-in identity. | Reconnect the assistant and sign in again. |
| Authentication not configured | The connector's backend identity link is not set up, or your account has no recorded Plant scope. | Contact AVA Asia. Retrying will not fix this. |
| Forbidden | The Plant ID is outside the connected account's access, or it does not exist. | Confirm the Plant ID from a discovery call, or ask your administrator to review access. |
| Invalid query | A date, interval, ID, or search text is not valid. This includes a 5min interval request, which is not supported. | Give a complete daily date range, a valid Plant ID, and a non-empty search query. |
| Query limit exceeded | The result would exceed 1,000 rows or 1 MB of serialized data. | Ask for a smaller date range. |
| Unavailable | The SolarSENS Public API could not be reached or rejected the request. | Retry later or narrow the request. |
| Upstream invalid response | The Public API returned data the connector could not parse. | Retry later. Contact AVA Asia if it persists. |
An empty result is not proof that production was zero. Check coverage and warnings before drawing a conclusion.
Cloudflare Error 1010
Some HTTP libraries send a default User-Agent that Cloudflare blocks with
"Error 1010", for example Python's urllib. This replaces the normal MCP
error response with a Cloudflare block page. Not every non-browser client is
affected: curl and Node's default client reach the MCP endpoint normally.
Set a descriptive User-Agent, or use an MCP client, to avoid the block. See
Troubleshooting for the fix.