Prevent looping operations from polluting the logs

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: backend
    • None
    • Not defined

      Context: https://camunda.slack.com/archives/CUZUYDMMG/p1681988607037699

      There are sometimes operations that happen within Optimize that are constantly repeated. These can be identified either in while loops or by periodic triggers in scheduled services.

      It can happen that an exception being thrown in these loops causes the next loop to start right away. In the linked thread, this happened during a CI job running and the resulting logs were expensively polluted by the same logged message.

      We should implement retries/backoffs in such a scenario so the same exception isn't just repeatedly attempted

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: