mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #2883] Identity Management \ Administration \ Users \ All Tenants now produces timeout #1421
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#1421
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 @bandicootlimited on GitHub (Sep 4, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2883
Description
Select Identity Management \ Administration \ Users. Select All Tenants. After 3 minutes an error 'The Azure Function has taken too long to respond. Try selecting a different report or a single tenant instead 500 - Request failed with status code 500' appears.
The same report for All Tenants used to run OK in June July and August.
If I also reduce the tenants down to only two tenants by going to Settings \ CIPP \ Application Settings \ Tenants and setting all but two as Excluded. Return to Identity Management \ Administration \ Users. Select All Tenants I get the same error.
Environment data
@github-actions[bot] commented on GitHub (Sep 4, 2024):
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!".
@bandicootlimited commented on GitHub (Sep 4, 2024):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@bandicootlimited commented on GitHub (Sep 6, 2024):
It worked once Thursday morning. Other than that failed maybe 300 times on different computers different browsers, including setting to exclude all but two tenants. Times out after 3 minutes. Was working fine in August.
@KelvinTegelaar commented on GitHub (Sep 8, 2024):
This is a support issue, not a bug.