Savin

correct - you might be running into [this](https://docs.metaflow.org/metaflow/basics#data-flow-through-the-graph) expected behavior. The link has details on how to correctly move state through a foreach. Let me know if that works!

@bjupreti are you able to replicate this error consistently?

yep - `insert_name_here.py --production step-functions trigger`

`trigger` also passes in the parameters to the step-function. you can always do `insert_name_here.py --production step-functions trigger --param True`

@rsmith013 can you help me with the before and after for the error message

One workaround that wouldn't require any changes to metaflow would be to create a pure python decorator whose behavior can be controlled using environment variables. Here is an approach -...

Thanks! Let's chat async about the contents and the structure of the message before shipping this PR. It would be good to embed link to the UI in the message...

that's a great idea! anybody who comes across this issue, please give a 👍🏼 if you would like this to be prioritized on the roadmap.

@derfred - Is there any reason for the TTL to be only scoped to Kubernetes Jobs and not pods?

That's a great idea. Today, if you want a bird's eye view of any run's state, you can click on a lever button towards the very right of the row...