Lukáš Novotný

+1 I was just looking for a similar thing. Sometimes you just know no matter how much you retry it will always fail. By the way, you might be able...

Actually the version `0.15.5` is the one that broke it. I've put some debug logs here https://github.com/PrefectHQ/prefect/blob/5fee7a791d2448d9a7919722edb368c4ba905a19/src/prefect/client/client.py#L2155 From unmapped run (works): ``` {'mutation($input: create_task_run_artifact_input!)': {'create_task_run_artifact(input: $input)': {'id'}}} {'input': {'task_run_id': '65f55244-948d-4e38-88c1-d6eb7cf82dba',...

I'm running it in locally deployed server + local agent - `prefect server start` + `prefect agent local start --show-flow-logs`

Hey, thanks @nneuh07, looks like you found the bug already, thanks for that! https://github.com/PrefectHQ/prefect/issues/5309#issuecomment-1010318486 > This could indicate a storage issue because the CLI registers the flow with script storage...

Observing the same issue as you, if you're using `Table` for state, there is a similar discussion in this [slack thread](https://fauststream.slack.com/archives/C7FL9CB5E/p1616151289034300). > we use the threaded producer for the changelogs...

I think this is because the expiration logic https://github.com/faust-streaming/faust/blob/63af9f58dfb5159bea6e5c8a0312bc41627d9538/faust/tables/base.py#L374-L390 depends on `self._partition_timestamp_keys` which is populated only in `_maybe_set_key_ttl` https://github.com/faust-streaming/faust/blob/63af9f58dfb5159bea6e5c8a0312bc41627d9538/faust/tables/base.py#L400 which is triggered only in `on_key_set` callback. https://github.com/faust-streaming/faust/blob/96ce8f0b2f213b296bab2b4c2c0feea37a412ed7/faust/tables/table.py#L75-L83 I suspect that...