Hey Team, When our agents go down due to a hosed host, we find that we can get an email notification via automations setup (agent is unhealthy). However, when we change it to pagerduty, we find we do not get alerts. How can we resolve this?

Hey @Charles Leung, was the schedule of these flows created before the pagerduty alert was created

Hey Kevin this is not a flow alert, this is an unhealthy agent alert

Hi Charles - have you confirmed that the pagerduty action works with other automations or with the test_action mutation: Find action ID by running:

query {
  action {
    id
    name
    action_type
  }
}

Then you can test the action by using:

mutation {
  test_action (input: {action_id: ""}){
    success
  }
}

Hey Jenny! Yes we have pagerduty actions on our flows that work great

Hmmm... Are there any messages about that automation in your notifications tile on the dashboard?

@Callum Okuefuna Hey Callum! Jenny is assisting us with this issue - could you provide detail if you've seen any notifications on this?

I haven't seen anything to do with unhealthy agent via pagerduty. The test I performed was to attach the agent to a config-group and bring it down, and we got no notifications through

hI @Callum Okuefuna - can you check the notifications tile on your dashboard - if there's an issue with an automation we send a message there. If there's a notification there it should give us more info to work from.

Hey Jenny! Thanks this is resolved now - we are working on integrating it with our ansible roles.

Great. Thanks for the udpate!