New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CustomWebhook block type not found on Automation action #13282
Comments
@robfreedy at the moment only known system block types (like We don't have any way to instantiate Happy to chat through a feature request if you think there's value. Seems like at minimum we could explain the above in our Automations action error message. |
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 I would maybe propose we either:
cc: @masonmenges |
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: