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

Hi we are running flows via a k8s agent and we are trying to disable checkpointing. We are using a k8s yaml template that sets the environment variable `PREFECT__FLOWS__CHECKPOINTING: false` for the flow. Based on the logs/errors we are seeing - the flow is still trying to serialize and write results. Two questions:
1. if we disable checkpointing at the flow level should prefect core _not_ attempt to serialize the result
2. what is the appropriate way to disable checkpointing at the flow level
Relevant traceback included as a comment from when we ran a job where the env var was set to false

```[2021-03-03 17:53:38+0000] ERROR - prefect.CloudTaskRunner | Unexpected error: TypeError("can't pickle _thread.lock objects")
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/prefect/engine/runner.py", line 48, in inner
    new_state = method(self, state, *args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/prefect/engine/task_runner.py", line 891, in get_task_run_state
    result = self.result.write(value, **formatting_kwargs)
  File "/usr/local/lib/python3.7/dist-packages/prefect/engine/results/s3_result.py", line 100, in write
    binary_data = new.serializer.serialize(new.value)```


Hmmm, we currently hardcode that to on, but I'm not sure why.

I assume you didn't set the `S3Result` yourself, and its instead set automatically from `S3` storage?

We got around this by setting each task to checkpoint=False

We should be able to support this though. I'll raise an issue.

<@ULVA73B9P> open "Support disabling checkpointing at the flow level"

<https://github.com/PrefectHQ/prefect/issues/4201>

Actually, if you set `{"checkpointing": False}` in the context for a flow run, that should work.

`PREFECT__CONTEXT__CHECKPOINTING=false` might also work

Interesting thanks for the response - I’m not sure we’re going to get around to testing that soon but we will definitely keep this in mind when we get back to this on our end

NVM, it's hardcoded in a different spot than I remembered, none of the above will work.