<@ULVA73B9P> what do you make of this? ```{ "id"...
# ask-marvin
j
@Marvin what do you make of this?
Copy code
{
  "id": "f0d21b9d-270a-450f-962e-9bcfcbd4fff7",
  "account": "86eb4016-3bda-40df-a926-a5da355f8393",
  "event": "prefect-cloud.automation.action.failed",
  "occurred": "2024-11-04T23:22:17.759Z",
  "payload": {
    "action_index": 0,
    "action_type": "send-notification",
    "invocation": "6347154b-4dad-4d1f-9520-13f4ab0963f9",
    "reason": "Notification failed",
    "notification_log": "[ERROR]: There are no service(s) to notify"
  },
  "received": "2024-11-04T23:22:17.760Z",
  "related": [
    {
      "prefect.resource.id": "prefect.block-document.3d5362cd-9a48-4324-8aaa-c47ccb677361",
      "prefect.resource.role": "block",
      "prefect.resource.name": "prefect-channel"
    },
    {
      "prefect.resource.id": "prefect.block-type.ms-teams-webhook",
      "prefect.resource.role": "block-type"
    }
  ],
  "resource": {
    "prefect.resource.id": "prefect-cloud.automation.5655ff67-d7ba-472e-a65f-5848c2d31c2c",
    "prefect.resource.name": "Main Flow Failure Notifications",
    "prefect-cloud.trigger-type": "event",
    "prefect-cloud.posture": "Proactive"
  },
  "workspace": "5c4b372e-3f1b-4fed-a973-09381e72d9e2"
m
Your message was too long by 115 tokens - please shorten it and try again. For reference, here's your message at the allowed limit:
what do you make of this?
```{ "id": "f0d21b9d-270a-450f-962e-9bcfcbd4fff7", "account": "86eb4016-3bda-40df-a926-a5da355f8393", "event": "prefect-cloud.automation.action.failed", "occurred": "2024-11-04T232217.759Z", "payload": { "action_index": 0, "action_type": "send-notification", "invocation": "6347154b-4dad-4d1f-9520-13f4ab0963f9", "reason": "Notification failed", "notification_log": "[ERROR]: There are no service(s) to notify" }, "received": "2024-11-04T232217.760Z", "related": [ { "prefect.resource.id": "prefect.block-document.3d5362cd-9a48-4324-8aaa-c47ccb677361", "prefect.resource.role": "block", "prefect.resource.name": "prefect-channel" }, { "prefect.resource.id": "prefect.block-type.ms-teams-webhook", "prefect.resource.role": "block-type" }
j
> @Marvin what do you make of this? { "id": "...", "account": "...", "event": "prefect-cloud.automation.action.failed", "occurred": "2024-11-04T232217.759Z", "payload": { "action_index": 0, "action_type": "send-notification", "invocation": "6347154b-4dad-4d1f-9520-13f4ab0963f9", "reason": "Notification failed", "notification_log": "[ERROR]: There are no service(s) to notify" }, "received": "2024-11-04T232217.760Z", "related": [ { ... }, { "prefect.resource.id": "prefect.block-type.ms-teams-webhook", "prefect.resource.role": "block-type" } ], "resource": { ... }, "workspace": ...
m
Your message was too long by 3 tokens - please shorten it and try again. For reference, here's your message at the allowed limit:
> what do you make of this?
```{ "id": "f0d21b9d-270a-450f-962e-9bcfcbd4fff7", "account": "86eb4016-3bda-40df-a926-a5da355f8393", "event": "prefect-cloud.automation.action.failed", "occurred": "2024-11-04T232217.759Z", "payload": { "action_index": 0, "action_type": "send-notification", "invocation": "6347154b-4dad-4d1f-9520-13f4ab0963f9", "reason": "Notification failed", "notification_log": "[ERROR]: There are no service(s) to notify" }, "received": "2024-11-04T232217.760Z", "related": [ { "prefect.resource.id": "prefect.block-document.3d5362cd-9a48-4324-8aaa-c47ccb677361", "prefect.resource.role": "block", "prefect.resource.name": "prefect-channel" }, { "prefect.resource.id": "prefect.block-type.ms-teams-webhook", "prefect.resource.role": "block-type
Ah, it appears you have a JSON object representing an event from Prefect Cloud where an automation action failed. Specifically, the action was of type "send-notification," and the failure reason is "Notification failed" due to "[ERROR]: There are no service(s) to notify." Here's a breakdown of the key information: - Event Type:
prefect-cloud.automation.action.failed
- Occurred: It occurred on November 4th, 2024. - Action Type: The action that failed is a "send-notification." - Reason for Failure: No services were available for notification. - Related Resource: It seems related to an MS Teams webhook block, indicated by the
"prefect.block-type.ms-teams-webhook"
resource. From this, it seems like the system attempted to send a notification, possibly via an MS Teams webhook, but there were no configured endpoints or services to send that notification to. This could be due to misconfiguration or perhaps a removal of the expected notification endpoints. If you'd like to troubleshoot this further or ensure proper setup, you may want to check your configuration for notification endpoints or any associated webhooks. If you're using Prefect 2.x or 3.x, I can dive into their documentation to help iron out the details or resolve this issue! Just let me know which version you're using.
j
> @Marvin Prefect 2. What do you mean by configuration for notification endpoints? Would this be something in ms teams?
m
In Prefect 2.x, you can set up notifications for various events, such as when a flow enters a specific state. Prefect supports multiple webhook integrations, including Microsoft Teams. To receive notifications via MS Teams, you would typically configure a webhook in Teams to receive messages from Prefect. Here's a summary of what you might need to do: 1. Set Up a Webhook in Microsoft Teams: Within your Teams channel, you can add an incoming webhook connector. This will give you a URL that receives POST requests from Prefect when specific events occur. 2. Configure Prefect Notifications: In Prefect Cloud, you'll need to set up a notification automation. This automation uses the Teams webhook URL to send notifications about flow state changes or other significant events. Prefect Cloud provides a robust interface for setting up these notifications, using its Automations feature. If you're hosting your Prefect server, there's a more limited option available for notification configuration. For more detailed instructions, you can refer to the following Prefect 2.x documentation on notifications and webhooks: Prefect 2.x Notifications Documentation. It's essential to ensure the webhook URL in Teams is correctly set up and that your Prefect notification automation is properly configured to utilize it. "No service(s) to notify" suggests that there might not be any endpoint URL configured, or the integration settings haven't been completed. If you treat configuring webhooks like leaving your house keys behind, then remember: having the right configuration might just be the key to unlocking seamless notifications! 🎹
b
Hi James! Are you using the Microsoft teams webhook in an automation by chance?
TL;DR We haven't switched over microsoft teams webhooks in cloud (yet). the generic webhook block should unblock you until the switch is complete!
j
Thank you!
🙌 1