DagsterCloudHTTPError: 413 Client Error: Request Entity Too Large for url: ­https://{org}.agent.dagster.cloud/graphql

Last updated: October 9, 2025

Problem

You see a 413 Client Error in the run logs:

dagster_cloud_cli.core.errors.DagsterCloudHTTPError: 413 Client Error: Request Entity Too Large for url: ­https://{org}.agent.dagster.cloud/graphql

Example error

dagster_cloud_cli.core.errors.DagsterCloudHTTPError: 413 Client Error: Request Entity Too Large for url: ­https://fanatics-live.agent.dagster.cloud/graphql: <html>
<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx</center>
</body>
</html>
...
 File "/venvs/3ee845f93feb/lib/python3.10/site-packages/dagster/core/events/init_.py", line 1035, in asset_check_evaluation
    return DagsterEvent.from_step(
  File "/venvs/3ee845f93feb/lib/python3.10/site-packages/dagster/core/events/init_.py", line 472, in from_step
    log_step_event(step_context, event, batch_metadata)

Possible causes

This class of error can arise when an error log returned in a failed step is >5MB.

It can also occur when an asset check evaluation returns >5MB of metadata.