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

Untitled.txt

Hi Prefect Team, I would love your thoughts on if this is the Prefect way on doing this.

I have a scheduled flow where we need a `run_date` that is yesterday UTC time. I would love to use the prefect context to do this and this worked for me, but is there a better way?

Hi <@ULXTHLCLU> - modifying `context` within a Task is not recommended, and `context` should be treated as read-only (unless you are adding values to context through environment variable or the API).

Why do you need to add this to context?  You can always compute it within any task, as you did above:
```run_date = prefect.context.date.date() - datetime.timedelta(days=1)```

Thanks <@UKNSNMUE6>, we have multiple different load tasks that all require this same date value.

Rather than calculate each time, and introduce another place this could go wrong, I would rather do it once for all the tasks to access. Similar in style to how you make `date` available via context

Gotcha gotcha; in that case I recommended creating a single task that computes this date and returns it as a piece of data for downstream tasks to consume directly from a kwarg

Ahhhh cool that was our original implementation