Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
None
-
None
Description
Ryan Rumbaugh
Today at 9:34 AM
Hi all, Nebraska is working through our term rollover right now and we ran into something new after all these years!
After updating course loaders we noticed the CHANGE_LOG_consumer_findBadMemberships job began failing and appeared to be stalled. Turns out an access policy was created that used a course basis group in its allow group, but the composite group was disabled! After updating the begin date for the composite the findBadMemberships job started working again as expected.
A couple questions:
Should a disabled group stall out the processing of findBadMemberships? It strikes me as a bug, but maybe it is working as designed.
If the access policy was using a ref group instead of a basis group, would this occur?
Thanks!
1 reply
Chris Hyzer
< 1 minute ago
seems like a bug... we will work on it. I dont think ref vs basis would help...