[GH-ISSUE #1788] Halo Webhooks for Alerts not working #947

Closed
opened 2026-03-02 12:46:31 +03:00 by kerem · 4 comments
Owner

Originally created by @BNWEIN on GitHub (Oct 6, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1788

Description

Halo Webhooks for CIPP > Settings > Notifications are working fine

Halo Webhooks for Alert Policies are not. Error 400 as previously discussed in Discord.

Environment data

Back end and front end: 4.3.1
Tenant cache not relevant.
Token cache also not relevant.
Originally created by @BNWEIN on GitHub (Oct 6, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1788 ### Description Halo Webhooks for CIPP > Settings > Notifications are working fine Halo Webhooks for Alert Policies are not. Error 400 as previously discussed in Discord. ### Environment data ```PowerShell Back end and front end: 4.3.1 Tenant cache not relevant. Token cache also not relevant. ```
kerem 2026-03-02 12:46:31 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 6, 2023):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:1750411969 --> @github-actions[bot] commented on GitHub (Oct 6, 2023): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/ If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.". Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@BNWEIN commented on GitHub (Oct 6, 2023):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug

<!-- gh-comment-id:1750412204 --> @BNWEIN commented on GitHub (Oct 6, 2023): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug
Author
Owner

@KelvinTegelaar commented on GitHub (Oct 9, 2023):

Resolved in dev. Waiting for confirmation.

<!-- gh-comment-id:1752903031 --> @KelvinTegelaar commented on GitHub (Oct 9, 2023): Resolved in dev. Waiting for confirmation.
Author
Owner

@KelvinTegelaar commented on GitHub (Oct 10, 2023):

considering fixed

<!-- gh-comment-id:1755363899 --> @KelvinTegelaar commented on GitHub (Oct 10, 2023): considering fixed
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#947
No description provided.