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

On version 0.9.8 and received this error during testing:
``` Unexpected error: AttributeError("'S3ResultHandler' object has no attribute '_client'")```
any thoughts?

What are you testing for this to occur? The `_client` attribute was updated in this recent PR <https://github.com/PrefectHQ/prefect/pull/2136> and I wonder if there’s a chance it’s being referenced before assignment

Im running an end-to-end test of a workflow but further review of the code I realize that the handler is not referenced in any of the task

:thinking_face: so the issue is happening without initializing the handler at all?

I do initialize the result handler but I dont place the object in the task definition

Are you initializing it similar to this?
```In [21]: S3ResultHandler(bucket='my-bucket')
Out[21]: &lt;ResultHandler: S3ResultHandler&gt;

In [22]: r = _

In [23]: r.client
Out[23]: &lt;botocore.client.S3 at 0x10cc10908&gt;

In [24]: r._client
Out[24]: &lt;botocore.client.S3 at 0x10cc10908&gt;```

```RESULT_HANDLER = S3ResultHandler(
    bucket='workflow-output',
    aws_credentials_secret='AWS_CREDS',
)```

but then the object is not used anywhere in the workflow code

Does the error happen there when you initialize or when you run your flow?

Weird I’m really not sure how that error would be raised if your flow does not use the S3ResultHandler anywhere

any suggestions for `0.9.8` ? I have already moved back to `0.9.7`

Do you happen to have a reproduceable example that encounters this?

Hey josh, I now see what is going on with this result_handler

I have two workflows: one with retries and the other without. The workflow with retries requires a result_handler at the Flow level. Now on version `0.9.8` and `0.9.7` I am getting the `Unexpected error: AttributeError("'S3ResultHandler' object has no attribute '_client'")` error

also seems to occur the first time for a mapping task

Hi <@UL39052F5> . I met the same error on 0.9.8 and wondering if you have figured it out. Our S3ResultHandler is also set on the flow level.