Symptom
- SAC stories are not getting executed.
- Error shown in story: “Failed to fetch data.”
- Error shown in some cases: “Cannot reach the remote system. It may be offline.”
- Browser traces show HTTP 404 on GET /sap/public/bw/ina/storageaccess/request.html.
- Browser traces show HTTP 403 Forbidden on POST /sap/bw/ina/GetResponse.
- Some stories on the same backend work, while others fail (including when switching the live connection target).
Environment
- SAP Analytics Cloud 2026.2.6 -> 2026.2.10.
Reproducing the Issue
- Open a story that uses a live data connection.
- Provide required variables/filters for the underlying model.
- Run or refresh the story.
- Observe the message “Failed to fetch data.” In developer tools, network calls may show 403/404 on BW INA endpoints.
Cause
The customer's AWS WAF was blocking requests containing /sap/bw on the Fiori Load Balancer, causing legitimate traffic to be denied.
Resolution
The cusotmer's basis team added an exception rule in AWS WAF to allow
/sap/bw requests. After the exception was applied, the functionality resumed working normally.See Also
- 3565162 - How to configure Cross-Origin Resource Sharing (CORS) for live data connections to BW - SAP Analytics Cloud
- Live Data Connection to SAP BW using a CORS connection via Unified Connectivity
- 1787981 - Service connection "HTTP-based Tools"
- 2280022 - How to collect a HTTP archive (HAR) file and Console Log file in SAP Analytics Cloud
- 2538909 - How to export / move / copy / transport content and data between two tenants in SAP Analytics Cloud
Keywords
sac story, failed to fetch data, cannot reach the remote system, live connection, cors, bw ina, getresponse, storageaccess, 403 forbidden, 404 not found, sicf, trusted origins, preflight options, samesite none secure, http-based tools connection , KBA , LOD-ANA-DES , Story Design & Visualizations , Problem
Product
SAP Analytics Cloud 1.0
SAP Knowledge Base Article - Public