Hi All,
We are facing a lot of GraphQL errors in Dagit due to the large number of underlying data stored in the PostgreSQL database (see screenshot for the details). I have already increased the statement timeout for Dagit, however, this does not solve the underlying problem! Is there a way to set data retention for the "runs" table created by Dagster inside the PostgreSQL database or some other solution in order to avoid the GraphQL errors to happen (implementing a more specific LIMIT inside the query for instance, not sure what the current LIMIT does as there is no information regarding "param_1")?
*Note that this GraphQL error not only occur at the schedules, but almost everywhere within the Dagit UI!
Would love to hear your reaction to this!
Kind regards,
Arnoud