# Dagster: Some asset runs failing with a "GraphQLStorageError: Error in GraphQL Response" error

- Impact (vendor’s label): major
- Status: resolved
- Started: 2023-09-06 19:30 UTC · Resolved: 2023-09-06 23:59 UTC · Duration: 4.5 h
- Updates: 4 · Affected components: API
- [Vendor status page: https://stspg.io/gtj476t1k08m](https://stspg.io/gtj476t1k08m)
- [Company: Dagster](https://rewindex.com/company/dagster.md)

## Summary

Some Dagster asset runs failed with GraphQLStorageError errors as storage-engine timeouts increased during execution, affecting the API. The vendor rated the incident major; it ran from 2023-09-06 19:30 UTC to 2023-09-06 23:59 UTC, lasting 4 h 29 min. A fix was implemented and the incident was resolved. _(machine-written, sol)_
## Timeline of updates

- **investigating** 2023-09-06 19:30 UTC: We have observed an increase in timeouts from our storage engine during run execution, resulting in some runs failing with an error like the following in the event log: dagster\_cloud\_cli.core.errors.GraphQLStorageError: Error in GraphQL response: \[{'message': 'Internal Server Error (Trace ID: XXX)', 'locations': \[{'line': 22, 'column': 13}\], 'path': \['eventLogs', 'getEventRecords'\]}\] We are currently investigating the issue.
- **identified** 2023-09-06 20:08 UTC: The issue has been identified and we are in the process of testing a fix.
- **monitoring** 2023-09-06 22:39 UTC: A fix has been implemented and we are monitoring the results.
- **resolved** 2023-09-06 23:59 UTC: This incident has been resolved.

## Rewindex changes for this incident

- 2023-09-06 19:30 UTC: [Major incident: Some asset runs failing with a "GraphQLStorageError: Error in GraphQL Response" error](https://rewindex.com/change/i5d4cf578b0bb69.md)


---
Canonical: https://rewindex.com/company/dagster/incidents/2fhnny9w2q0h · Markdown: https://rewindex.com/company/dagster/incidents/2fhnny9w2q0h.md · JSON: https://rewindex.com/api/v1/companies/dagster/incidents/2fhnny9w2q0h · Generated 2026-10-18T10:41:18.316Z