starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #5262] [Bug]: Drift notification email behavior #2529

New issue

Closed

opened 2026-03-02 13:53:05 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:53:05 +03:00

Owner

Originally created by @thechaosmanor on GitHub (Jan 23, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5262

Required confirmations before submitting

I can reproduce this issue on the latest released versions of both CIPP and CIPP-API.
I have searched existing issues (both open and closed) to avoid duplicates.
I am not requesting general support; this is an actual bug report.

Issue Description

We are receiving drift notifications for customers who are not within scope of the drift policy. As it happens, this drift policy does not currently have any tenants assigned to it at the moment. It had one when it was first created, but we removed that tenant from the policy, and it's not assigned to a classic standard either. The notifications for the drift policy drift are coming up for three tenants assigned to a classic standard, and one assigned to no standard at all.

Environment Type

Front End Version

v10.0.3

Back End Version

v10.0.5

Relevant Logs / Stack Trace

Originally created by @thechaosmanor on GitHub (Jan 23, 2026). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5262 ### Required confirmations before submitting - [x] **I can reproduce this issue on the latest released versions** of both CIPP and CIPP-API. - [x] **I have searched existing issues** (both open and closed) to avoid duplicates. - [x] I am **not** requesting general support; this is an actual bug report. ### Issue Description We are receiving drift notifications for customers who are not within scope of the drift policy. As it happens, this drift policy does not currently have any tenants assigned to it at the moment. It had one when it was first created, but we removed that tenant from the policy, and it's not assigned to a classic standard either. The notifications for the drift policy drift are coming up for three tenants assigned to a classic standard, and one assigned to no standard at all. ### Environment Type Sponsored (paying) user ### Front End Version v10.0.3 ### Back End Version v10.0.5 ### Relevant Logs / Stack Trace ```plaintext ```

kerem

2026-03-02 13:53:05 +03:00

closed this issue
added the
bug

unconfirmed-by-user

not-assigned
labels

kerem commented

2026-03-02 13:53:06 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 23, 2026):

Thank you for reporting a potential bug. If you would like to work on this bug, please comment:

I would like to work on this please!

Thank you for helping us maintain the project!

@github-actions[bot] commented on GitHub (Jan 23, 2026): Thank you for reporting a potential bug. If you would like to work on this bug, please comment: > I would like to work on this please! Thank you for helping us maintain the project!

kerem commented

2026-03-02 13:53:06 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Feb 8, 2026):

You should not have any standards with no tenants assigned. In the next version this will be actively blocked.

@KelvinTegelaar commented on GitHub (Feb 8, 2026): You should not have any standards with no tenants assigned. In the next version this will be actively blocked.

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#2529

No description provided.

Rows
Columns