---
title: Troubleshooting
---

# Troubleshooting

This page covers common issues across alert configuration, Slack integration, and webhook delivery. Each entry lists the symptom, its most likely cause, and the recommended resolution.

---

## Alert configuration issues

**1. The Attach button is unavailable for my resource.**

The alert can only be attached to resources in the **Running** state. Check the resource status in the console and retry once it is active.

---

**2. I created an alert but no notifications are being sent.**

- Verify the alert is attached to the resource. Creating an alert does not automatically attach it.
- Confirm the resource is in the **Running** state and the metric threshold has actually been crossed.
- Check that the Monitoring Integration has at least one valid destination (email address, Slack channel, or webhook URL).
- Use the **Test** button on the Monitoring Integration to verify the destination is reachable.

---

**3. I cannot change the Service Type after creating an alert.**

Service Type is fixed at creation and cannot be modified. If you need a different service type, delete the alert and create a new one with the correct configuration.

---

**4. The same alert is not firing again after it was resolved.**

Alerts re-fire each time the condition is met again after a resolved state. If no re-fire is observed, confirm the metric crossed the threshold again by reviewing resource metrics.

---

**5. Deleted button on Monitoring Integration is disabled.**

Monitoring Integration can not be deleted unless they are associated with an alert. First remove that monitoring integration from the alert and then delete it.

---

## Slack integration issues

| Symptom | Likely cause | Resolution |
|---|---|---|
| Test message not received (webhook method) | Webhook URL is incomplete or invalid | Recopy the full URL from the Slack app dashboard under Incoming Webhooks |
| Test message not received (token method) | Bot has not been invited to the channel | Run `/invite @YourAppName` in the target channel |
| `channel_not_found` error | Incorrect Channel ID entered | Use the Channel ID (e.g. `C12345678`), not the channel name |
| Alerts stop delivering after working previously | Webhook URL was regenerated | Update the Webhook URL in the Monitoring Integration settings |
| `missing_scope` error | Bot Token is missing the `chat:write` scope | Add `chat:write` under OAuth & Permissions and reinstall the app |
| Messages delivered to the wrong channel | Incorrect Channel ID or webhook scoped to a different channel | Verify the Channel ID or recreate the webhook for the correct channel |
| Bot posts in public channels but not private ones | Bot not invited to the private channel | Run `/invite @YourAppName` inside the private channel |

---

## Webhook integration issues

| Symptom | Likely cause | Resolution |
|---|---|---|
| No webhook request received | Endpoint URL is incorrect or unreachable | Verify the URL is publicly accessible and accepts POST requests |
| `401 Unauthorized` response from endpoint | Missing or invalid `Authorization` header | Ensure the token in the `Authorization` header matches what your endpoint expects |
| Webhook received but payload not parsed correctly | Endpoint not handling JSON body | Ensure your endpoint reads the request body as `application/json` |
| Delivery marked as failed | Endpoint returned a non-`2xx` status code | Return a `200 OK` immediately after receiving the request |
| Notifications arrive but with a delay | Endpoint processing time is too long | Acknowledge the request immediately with `200 OK` and process asynchronously |
| Test delivery succeeds but live alerts do not arrive | Firewall or IP allowlist blocking production traffic | Allowlist the alert delivery IP range for your environment |

---

## Email integration issues

**Notification emails are not arriving.**

- Check the spam or junk folder for the recipient addresses.
- Verify that all email addresses in the Monitoring Integration are valid and correctly entered.
- Confirm the alert is attached to a running resource and that the threshold condition has been met.
- Use the **Test** button on the Monitoring Integration to send a test email and confirm delivery.

---

**I am receiving duplicate email notifications.**

An alert is associated with multiple Monitoring Integrations that share the same recipient address. Review the Monitoring Integrations attached to the alert and remove duplicates.

---

## General

**The Test button on the Monitoring Integration shows success but I receive nothing.**

- For email: check spam and verify the address is correct.
- For Slack (webhook): confirm the webhook URL is still valid and has not been regenerated.
- For Slack (token): confirm the bot is still a member of the target channel.
- For webhook: confirm the endpoint is online and returning a `2xx` response.

---

**An alert was firing but has now disappeared from the Alerts panel.**

The alert was likely detached or deleted. Alerts can be removed from the Manage Alerts view or detached from the resource's Alert tab. Check both locations.

---

**I cannot find the Alert tab on a resource.**

The Alert tab is only visible on resources that support alert attachment: **Instances**, **Inference** services, and **Training Cluster** deployment jobs. Other resource types do not support alerts.


---