Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

[:heavy_check_mark: solved]
Hey Folks, Any tips on how to start digging into this error:

```Failed to write log with error: 413 Client Error: Payload Too Large for url: <http://dataflow-apollo:4200/graphql//graphql>```
The flow hadn't even run the first task, which was a `EnvVarSecret` .  Other instances of the Flow have run successfully.

Looking in the apollo logs I see the following:

```2020-12-14 09:50:26.951 GMT PayloadTooLargeError: request entity too large
    at readStream (/apollo/node_modules/raw-body/index.js:155:17)
    at getRawBody (/apollo/node_modules/raw-body/index.js:108:12)
    at read (/apollo/node_modules/body-parser/lib/read.js:77:3)
    at jsonParser (/apollo/node_modules/body-parser/lib/types/json.js:135:5)
    at Layer.handle [as handle_request] (/apollo/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/apollo/node_modules/express/lib/router/index.js:317:13)
    at /apollo/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/apollo/node_modules/express/lib/router/index.js:335:12)
    at next (/apollo/node_modules/express/lib/router/index.js:275:10)
    at cors (/apollo/node_modules/cors/lib/index.js:188:7)
2020-12-14 09:52:50.951 GMT Killed
Error
2020-12-14 09:52:50.954 GMT npm ERR! code ELIFECYCLE
2020-12-14 09:52:51.048 GMT npm ERR! errno 137
2020-12-14 09:52:51.049 GMT
npm ERR! @ serve: `node dist/index.js`
2020-12-14 09:52:51.049 GMT
npm ERR! Exit status 137
2020-12-14 09:52:51.049 GMT
npm ERR!
Error
2020-12-14 09:52:51.049 GMT
npm ERR! Failed at the @ serve script.
2020-12-14 09:52:51.049 GMT
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.```

Putting this down to resource limits on the apollo service.  I have bumped them up and will attempt to do the load that I was trying that caused this in the first place.

Increasing the cpu and memory limits have fixed the problem.