You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the GitHub search to find a similar issue and didn't find it.
I searched the Prefect documentation for this issue.
I checked that this issue is related to Prefect and not one of its dependencies.
Bug summary
Send a Notification Automation Action with CustomWebhook block fails after being triggered because the Block type could not be found. The CustomWebhook block does not exist out of the box in Prefect Cloud, so the block had to be registered to the workspace.
Reproduction
Register the Custom Webhook block using the command and python code below
Create the block by running the python code below
Create an automation with any trigger (used flow run state as completed for this example)
Set the Automation Action to "Send a notification" and specify the created Custom Webhook Block for the block. Save the automation.
Gotcha, that makes sense. I could see this experience being confusing based on what is exposed in the Cloud UI just because there could be any number of custom blocks with the "notify" tag on them when setting the block for the "Send a Notifaction" action that would not be valid since there is no way to instantiate the CustomWebhookNotificationBlock or any custom block type.
I would maybe propose we either:
Have a set list of "notification" block types that can be set on the Automation Action for sending a notification.
Support any block type (including custom block types) in the automation action (larger feature request/discussion)
First check
Bug summary
Send a Notification Automation Action with CustomWebhook block fails after being triggered because the Block type could not be found. The CustomWebhook block does not exist out of the box in Prefect Cloud, so the block had to be registered to the workspace.
Reproduction
Creating the block:
Command to register the block
Error
This was taken from the event payload of the Automation action Failed event (see complete payload in screenshot below).
Versions
Additional context
Automation Action Failed event payload:
The text was updated successfully, but these errors were encountered: