Edit

Share via

Test notification troubleshooting guide.

  • Article

This article describes troubleshooting steps for error messages you may get when using the test action group feature.

Note

Azure Action Groups doesn't support the use of private links today. It is reccomended that customers use public network access to avoid any issues. For other networking issues ensure you are properly using the Action Group Service Tag.

Troubleshooting error codes for actions

The error messages in this section are related to these actions:

  • Automation runbook
  • Azure Function
  • Logic App
  • Webhook
  • Secure Webhook
  • ITSM

Note

Several errors could be due to a misunderstanding of your schema. Click here to learn more information about Common alert schema and Non-common alert schema.

Error Codes Troubleshooting Steps
HTTP 400: The <action> returned a 'bad request' error. Check the alert payload received on your endpoint, and make sure the endpoint can process the request successfully.
HTTP 400: The <action> couldn't be triggered because this alert type doesn't support the common alert schema. 1. Check if the alert type supports common alert schema.
2. Change the “Enable the common alert schema” in the action group action to “No” and retry.
HTTP 400: The <action> couldn't be triggered because the payload is empty or invalid. Check if the payload is valid, and included as part of the request.
HTTP 400: The <action> couldn't be triggered because Microsoft Entra auth is enabled but no auth context provided in the request. 1. Check your Secure Webhook action settings.
2. Check your Microsoft Entra configuration. For more information, see action groups.
HTTP 400: ServiceNow returned error: No such host is known Check your ServiceNow host url to make sure it's valid and retry. For more information, see Connect ServiceNow with IT Service Management Connector

HTTP 401: The <action> returned an "Unauthorized" error.
HTTP 401: The request was rejected by the <action> endpoint. Make sure you have the required authorization.		 1. Check if the credential in the request is present and valid.
2. Check if your endpoint correctly validates the credentials from the request.

HTTP 403: The <action> returned a "Forbidden" response.
HTTP 403: Couldn't trigger the <action>. Make sure you have the required authorization.
HTTP 403: The <action> returned a 'Forbidden' response. Make sure you have the proper permissions to access it.
HTTP 403: The <action> is "Forbidden".
HTTP 403: Couldn't access the ITSM system. Make sure you have the required authorization.		 1. Check if the credential in the request is present, and valid.
2. Check if your endpoint correctly validates the credentials.
3. If it's Secure Webhook, make sure the Microsoft Entra authentication is set up correctly. For more information, see action groups.
HTTP 403: The access token needs to be refreshed. Refresh the access token and retry. For more information, see Connect ServiceNow with IT Service Management Connector
HTTP 404: The <action> wasn't found.
HTTP 404: The <action> target workflow wasn't found.
HTTP 404: The <action> target wasn't found.
HTTP 404: The <action> endpoint couldn't be found.
HTTP 404: The <action> was deleted.		 1. Check if the endpoints included in the requests are valid, up and running and accepting the requests.
2. For ITSM, check if the ITSM connector is still active.
HTTP 408: The call to the <action> timed out.
HTTP 408: The call to the Azure App service endpoint timed out.		 1.Check the client network connection, and retry.
2. Check if your endpoint is up and running and can process the request successfully.
3. Clear the browser cache, and retry.
HTTP 409: The <action> returned a 'conflict' error. Check the alert payload received on your endpoint, and make sure the endpoint and its downstream service(s) can process the request successfully.
HTTP 429: The <action> couldn't be triggered because it is handling too many requests right now. Check if your endpoint can handle the requests.
2. Wait a few minutes and retry.
HTTP 500: The <action> encountered an internal server error.
HTTP 500: Couldn't reach the Azure <action> server.
HTTP 500: The <action> returned an 'internal server' error.
HTTP 500: The ServiceNow endpoint returned an 'Unexpected' response.		 Check the alert payload received on your endpoint, and make sure the endpoint and its downstream service(s) can process the request successfully.
HTTP 502: The <action> returned a bad gateway error. Check if your endpoint, and its downstream service(s) are up and running and are accepting requests.
HTTP 503: The <action> host isn't running.
HTTP 503: The service providing the <action> endpoint is temporarily unavailable.
HTTP 503: The ServiceNow returned Service Unavailable		 Check if your endpoint is up and running and is accepting requests.
The <action> couldn't be triggered because the <action> didn't succeeded after XXX retries. Calls to the <action> will be blocked for up to XXX minutes. Try again in XXX minutes. Check the alert payload received on your endpoint, and make sure the endpoint and its downstream service(s) can process the request successfully.

Troubleshooting error codes for notifications

The error messages in this section are related to these notifications:

  • Email
  • SMS
  • Voice
Error Codes Troubleshooting Steps
The email couldn't be sent because the recipient address wasn't found.
The email couldn't be sent because the email domain is invalid, or the MX resource record doesn't exist on the Domain Name Server (DNS).		 Verify the email address(es) is/are valid and try again.

The email was sent but the delivery status couldn't be verified.
The email couldn't be sent because of a permanent error.		 Wait a few minutes and retry. If the issue persists, file a support ticket.

Invalid destination number.
Invalid source address.
Invalid phone number.		 Verify that the phone number is valid and retry.
The message couldn't be sent because it was blocked by the recipient's provider. 1. Verify if you can receive SMS from other sources.
2. Check with your service provider.

The message couldn't be sent because the delivery timed out.
The message couldn't be delivered to the recipient.		 Wait a few minutes and retry. If the issue still persists, file a support ticket.
The message was sent successfully, but there was no confirmation of delivery from the recipient's device. 1. Make sure your device is on, and service is available.
2. Wait for a few minutes and retry.
The call couldn't go through because the recipient's line was busy. 1. Make sure your device is on, and service is available, and not busy.
2. Wait for a few minutes and retry.
The call went through, but the recipient did not select any response. The call might have been picked up by a voice mail service. Make sure your device is on, the line isn't busy, your service isn't interrupted, and call doesn't go into voice mail.
HTTP 500: There was a problem connecting the call. Contact Azure support for assistance. Wait a few minutes and retry. If the issue still persists, file a support ticket.

Note

If your issue persists after you try to troubleshoot, please fill out a support ticket here: Help + support - Microsoft Azure.

See Also