I have retry for my task as follows ``` task max retries=3 r

Question

I have retry for my task as follows ``` task max retries=3 retry delay=timedelta seconds=5 def write delta lookup table ``` My image build failed for the reason `ValueError Task lt Task write delta lookup table gt has retry settings but some upstream dependencies do not have result types See for more details ` Why the task retry require result types I am not passing values from one task to another Also retry example doesnt show the use of result type What am I missing here Any documentation with simple retry usecase will be very helpful

Chris White · Answer

Hi < Saranya Elumalai> what version of Prefect are you running on I believe we removed this check recently Regardless if you add ```from prefect engine results import LocalResult when you initialize your Flow Flow result=LocalResult ``` to your Flow initialization this check will not fail

Saranya Elumalai · Answer

< Chris White> Using prefect core 0 11 2 Does this version still check

Chris White · Answer

If you re running into the error it must the patch I provided above or upgrading your Core version should resolve the issue for you

Saranya Elumalai · Answer

thanks let me try localresult and update you

Saranya Elumalai · Answer

< Chris White> The build is successful but the task failed with the following error ```Unexpected error TypeError can t pickle SSLContext objects Traceback most recent call last File usr local lib python3 7 site packages prefect engine runner py line 48 in inner new state = method self state args kwargs File usr local lib python3 7 site packages prefect engine task runner py line 977 in get task run state result = self result write value filename= output prefect context ``` Here is my code ```with Flow f store etl result=LocalResult as flow company = write delta lookup table ``` ``` task max retries=3 retry delay=timedelta seconds=10 def get S3 connection ``` What am I missing here

Chris White · Answer

that code looks like an old version of Prefect you should confirm that your Docker image also has the newest version of Prefect installed Regardless tasks must return objects that are capable of being serialized by `cloudpickle` else there is no way to persist them to disk I see that you are creating an S3 client for situations like this we have a WIP for shareable non pickelable objects here <https github com PrefectHQ prefect pull 3139>

Saranya Elumalai · Answer

< Chris White> 1 Which code looks like old version 2 Both tasks get S3 connection and write S3 data facing the same issue when added retry What are the recommended task return types

Chris White · Answer

The traceback looks like it came from an old version of prefect anything that is capable of being serialized by cloudpickle is a valid return type most python objects satisfy this Database connections and client objects or anything that maintains a reference to such objects are generally not serializable

Anish Chhaparwal · Answer

hey < Saranya Elumalai> and < Chris White> i m facing a similar issue i have a function that returns the client object of mongodb I am unable to pass it to other tasks is there any work around

Chris White · Answer

Hi < Anish Chhaparwal> at the moment I suggest you recreate the client within each task to avoid this issue This PR will ultimately provide a better pattern for these sorts of situations in the future

Saranya Elumalai · Answer

Yes < Chris White> < Anish Chhaparwal> thats what I did

Anish Chhaparwal · Answer

okay Thanks for the quick response appreciate it