Hey :slightly_smiling_face:, According to the Git...
# prefect-cloud
m
Hey 🙂, According to the GitHub ticket, https://github.com/PrefectHQ/prefect/issues/14575 the Teams notification block has been updated to the new workflow URL. Thanks for that !!! 🙂 When this block is used directly in the flow code, the notification works correctly. However, it doesn't seem to work when this block is used in an automation. It still appears to only work with a webhook URL in this case. Is anyone else experiencing this issue?
n
hi @Michael Michael can you share what error message (if any) you see? perhaps the content of your failed automation?
m
Thank you for your feedback 🙂 My automation is only used to trigger a Teams notification in the event of a faulty flow. It looks like this (screenshots). Since we use the cloud, we do not see any logs related to faulty automations here. It seems to work with the webhook URL, but not the workflow URL. However, if the notification block is called directly in the code, the notification works with the new workflow URL. Perhaps a webhook URL is still required for notifications in an automation?
n
Since we use the cloud, we do not see any logs related to faulty automations here.
in your
Event Feed
you should be able to find the
prefect-cloud.automation.*
events by filtering for them
m
oh ok, I hadn't thought of that, thank you 🙂
Copy code
"payload": {
    "action_index": 0,
    "action_type": "send-notification",
    "reason": "Notification failed",
    "notification_log": "[ERROR]: There are no service(s) to notify"
  },
The strange thing is that we also use the same block in some places directly in the code. Sending works there.
n
thank you for that @Michael Michael - this one might be on us. i think we need to update the version we use server-side to run that block in an automation. i'll make sure an issue is created for this 👍
m
@Nate thanks 🙂