This has been happening for about a month as a consequence of the recommendation api being unable to reach CX Server. This is documented in T405004: High volume of requests from rec-api to cxserver fail with 503 service unavailable
Test Steps
Test Case 1: Verify Recommendation API Does Not Produce 'NoneType' AttributeError When CX Server Is Unreachable
- Trigger a recommendation API request that requires CX Server (e.g., a section or article recommendation request).
- Ensure CX Server returns a 503 response or is unavailable.
- Observe the API response.
- Review Logstash for associated logs tied to the request.
- ✅❓❌⬜ AC1: Confirm no unhandled exception (AttributeError: 'NoneType' object has no attribute 'keys') is generated.
QA Results - Logstash
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T408934#11374869 |

