mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #3938] [Bug]: Standards fail to run when 1 is corrupt #1769
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#1769
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 @Shadoxity on GitHub (Apr 8, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3938
Required confirmations before submitting
Issue Description
Applying standards fails for all standards.
Gives an error message
"Failed to start standards run for allTenants. Error: You cannot call a method on a null-valued expression."
We did complete reinstalls and got no where and tracked this down to an issue in 1 standard that was causing all of them to fail. After deleting this 1 standard, they all worked again.
We have seen multiple reports on the discord as well on this.
I am guessing it was an issue with it going from v1 to v2 standards.
Here is a redacted copy of the standards template that was causing the error.
Every time I import it, can replicate the same error across all standards failing.
Environment Type
Non-sponsored user
Front End Version
7.4.2
Back End Version
7.4.2
Relevant Logs / Stack Trace
@github-actions[bot] commented on GitHub (Apr 8, 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!
@KelvinTegelaar commented on GitHub (Apr 8, 2025):
this is fixed in dev, will be included in Fridays release :)