recentMembership jobs should not be subject to FailSafe logic

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: API, daemon
    • None

      It took several hours to sort out what was going on with a recent membership job failing. One part was a local data condition.
      The other part was that a "recent membership group" needed change in a way that violated the fail safe limits for a loader job.

       

      I think that is a bug.

      recentMembership jobs should be "reliable enough" (based on all the data being in/from Grouper) to not "get it wrong".
      I request two things:

      1. the ability to mark a loader job as "except from failsafe limits".
      2. default recentMembership jobs to be marked as "except from failsafe limits"

            Assignee:
            Chris Hyzer (upenn.edu)
            Reporter:
            Carey Black (osu.edu) (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: