Details

    • Type: Task
    • Status: Resolved
    • Priority: Low
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: metronome
    • Labels:

      Description

      In `JobRunServiceActor` when we receive `TriggerJob` message, we might decide to skip the run. If skipRun is true, we don't send any message to the sender, but there is `JobRunServiceDelegate` calling this actor using ask pattern - and this future is resolved only when it receives message from that actor.

      So my guess is that:

      • if there is already an existing run
      • the concurrency policy is forbid
      • someones trigger a new job run through API
      • that API request will timeout

      Proper fix is to reply to `sender()` also when skipping schedule.

        Attachments

          Activity

            People

            • Assignee:
              alenavarkockova Alena Varkockova
              Reporter:
              alenavarkockova Alena Varkockova
              Team:
              Orchestration Team
              Watchers:
              Alena Varkockova, Ken Sipe, Matthias Eichstedt
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: