starred/CIPP

Fork 0

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

[GH-ISSUE #4067] [Bug]: Message trace is capped out at 1000 emails and doesn't go past 3 days #1844

New issue

Closed

opened 2026-03-02 13:47:33 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:47:33 +03:00

Owner

Originally created by @AnthonyLaCioppaSimplicity on GitHub (May 7, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4067

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

I am trying to use the message trace filter, and it mentions that we can review logs up to 10 days old although our logs only go back 3 days and seem to cap out at 1000 emails

Environment Type

Front End Version

v7.5.3

Back End Version

v7.5.3

Relevant Logs / Stack Trace

Originally created by @AnthonyLaCioppaSimplicity on GitHub (May 7, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4067 ### 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 I am trying to use the message trace filter, and it mentions that we can review logs up to 10 days old although our logs only go back 3 days and seem to cap out at 1000 emails ![Image](https://github.com/user-attachments/assets/cc935f3f-0b14-4734-b288-1741b2c67292) ### Environment Type Sponsored (paying) user ### Front End Version v7.5.3 ### Back End Version v7.5.3 ### Relevant Logs / Stack Trace ```plaintext ```

kerem

2026-03-02 13:47:33 +03:00

closed this issue
added the
bug

unconfirmed-by-user

not-assigned
labels

kerem commented

2026-03-02 13:47:34 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 7, 2025):

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 (May 7, 2025): 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:47:34 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 8, 2025):

Hello,

Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding,
The CIPP Team

@github-actions[bot] commented on GitHub (May 8, 2025): Hello, Thank you for your interest in improving CIPP! To keep our development process focused and manageable, **feature requests are limited to paying users**. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support. When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP. While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "**I’d like to work on this!**" to assign the issue to yourself. **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment and we’ll reopen the issue. _Thank you for understanding,_ **The CIPP Team**

kerem referenced this issue

2026-03-02 13:58:22 +03:00

[PR #1844] [MERGED] Fixes for 404 links to the old docs #3446

kerem referenced this issue

2026-03-02 13:58:24 +03:00

[PR #1852] [MERGED] Dev to release - GDAP hotfix + new features #3451

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

No description provided.

Rows
Columns