mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #3959] [Bug]: Mailbox Archive Size Incorrect #1780
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1780
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Zacgoose on GitHub (Apr 14, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3959
Originally assigned to: @rvdwegen on GitHub.
Required confirmations before submitting
Issue Description
Mailbox archive size is incorrect. You can tell that by looking at the message count of 3 and in the Exchange Portal.
I have seen this behavour a couple times in the past but this particular user has had this issue since online archive was enabled.
Environment Type
Non-sponsored user
Front End Version
v7.5.0
Back End Version
v7.5.0
Relevant Logs / Stack Trace
@github-actions[bot] commented on GitHub (Apr 14, 2025):
Thank you for reporting a potential bug. If you would like to work on this bug, please comment:
Thank you for helping us maintain the project!
@Zacgoose commented on GitHub (Apr 14, 2025):
Further to this it seems its actually to do with the storage value returned by MS as when its gets over 1GB in size the CIPP interface is correct. We noticed with about 800MB of data in the archive CIPP formatted it as 800GB rather than 0.8GB or 800MB
@rvdwegen commented on GitHub (Apr 14, 2025):
Hi, could you share a few screenshots and use the "View API response" button to copy an example of a result object where its displaying correctly and where its displaying incorrectly? You can blank out any identifying information.
@Zacgoose commented on GitHub (Apr 16, 2025):
Here is an image, you can clearly see that the numbers are not correct (Size that is) but once the actual usage is more than 1GB it correctly shows the usage.
It might be a while before I can get API reponces for you but I am confident that you will be able to replicate it in your test environment.
@rvdwegen commented on GitHub (Apr 17, 2025):
That was a fun wild goose chase haha. Fixed in dev with thanks to @kris6673