I made a post in prefect discourse here about some unexpected behavior with regards to Prefect Blocks in the UI https://discourse.prefect.io/t/possible-ui-bug-when-updating-blocks/4026?u=kaustin9 I will summarize here as well. Our team manages a few json config blocks in prefect UI. We want to use a deployment trigger so that particular deployment is ran anytime a particular json block is saved to. A trigger like this for example { “match”: { “prefect.resource.name”: “fake-json-block” }, “match_related”: {}, “after”: , “expect”: [ “prefect.block.json.save.called” ], “for_each”: , “posture”: “Reactive”, “threshold”: 1, “within”: 0 } The trigger is dependent on the prefect.block.json.save.called event for the json block “fake-json-block”. It works -- Ie if I update the json block like so

from prefect.blocks.system import JSON
JSON(value=[1,5,7]).save("fake-json-block", overwrite=True)

the deployment triggers. The problem we are having is that most of the time we are updating these blocks directly in the UI. When that happens I am not finding any corresponding event in the event log that I can use to trigger a deployment run. I would expect an event like prefect.block.json.updated in the event log (like I see when I update automations) but I dont see anything when I update directly in the UI. Is this an oversight/bug or is this intended behavior?

Hey Kyle, this is an interesting case. We generate events on any block method call in the python client. We don't emit corresponding events when the UI makes those API calls to change block values. That said, I think there may actually be better ways to achieve what you're trying to do - can I ask you to DM me and we can chat on it real quick?