mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #2897] Template Library task stop running #1433
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#1433
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 @github-inosek-com on GitHub (Sep 14, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2897
Description
If a Tenant is selected as Template Library and contain duplicated policy with the same display name but different type, the "CIPP Template" located in the scheduler stop working. Here's the step to reproduce:
1.) Create a compliance policy called "iOS/iPadOS"
2.) Create a app protection policy called "iOS/iPadOS"
3.) Wait for next scheduled sync, it'll "partially" succeed
4.) Bug appears, scheduler won't run the task again.
Removing the "conflicting" policy, deleting the scheduler task, and recreating it resolve the issue.
Environment data
@github-actions[bot] commented on GitHub (Sep 14, 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!".
@github-inosek-com commented on GitHub (Sep 15, 2024):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@github-actions[bot] commented on GitHub (Sep 25, 2024):
This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.
@github-actions[bot] commented on GitHub (Oct 10, 2024):
This issue was closed because it has been stalled for 14 days with no activity.