I ve asked a similar question before but I have a bit better

Question

I ve asked a similar question before but I have a bit better summary of what I am trying to accomplish Original thread is here <https prefect community slack com archives CL09KU1K7 p1659389359820829> New angle to the question is basically I have a flow state handler function and I need it to behave differently based on something that happens during the flow run The specific example is basically I have a flow state handler that updates an external api with the status running of a flow This functionality is optional and controlled via an `external job id` parameter So if a flow is running and it is to be associated with some external job record the id is passed If the id is passed updates are made as part of the flow state handler marking the job done when the flow completes recording error messages etc The above is working great The flow transition handler is generic and simply checks for the existence of the parameter in the context The new use case is basically a flow that is triggered by some outside automation Part of the flows responsibility is to create the external job record get its ID and update it when the flow completes Meaning I dont have the parameter at the start Is there anyway to save some kind of information onto the flow within a task so that I can check for its existence within the flow state transition function I ve tried doing `flow add task Parameter external job id default=$res ` where `$res` is the result of a task that creates the job and returns the id half way though the flow I also tried setting it in the context directly within the task No luck

Kyle McChesney · Answer

Example flow code ```with Flow flow executor=LocalDaskExecutor state handlers= external job updater as flow input url = Parameter input url job name = Parameter job name default=None username = Parameter username default= system external job id = create job job name username with prefect context external job id=external job id inputs = load inputs input url process map inputs ```

Anna Geller · Answer

the KV Store sounds like something you may consider this is a Cloud only feature though

Kyle McChesney · Answer

hmmm is there any way to get a resource manger to function like a normal context manager I E get the task results states for any tasks called within the manager block

Anna Geller · Answer

gt get the task results states for any tasks you may solve this problem using ```get task run result``` example ```from prefect tasks prefect flow run import get task run result get task run result flow run id task slug map index= 1 poll time=5 ``` the resource manager already is a normal context manager just restrained by a DAG once you migrate to Prefect 2 this will no longer be an issue