Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3269

CronNormalizerUtil is not correctly converting crontab to spring cron expressions

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Fixed
    • L3 - Default
    • 3.0.0-alpha2, 3.0.0
    • None
    • backend

    Description

      Context:
      In SUPPORT-7101 a customer raised the issue that given a five field cron expression is configured for the history cleanup that should run every minute it is run every hour.
      This was caused due to the normalizer that convertes 5 field crontab expressions to 6 field spring cron expression appended a "*" field while it actually should have prepended a zero seconds field "0" (first field in spring cron expression is second, while first in crontab is minute)

      AT:

      • the described issue is fixed and the conversion prepends the second field as "0" for the internal spring expression

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            is related to

            Task - A task that needs to be done. OPT-3278 Document that users can use spring cron expression to define repeating tasks in Optimize

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Done

            Activity

              People

                Unassigned Unassigned
                sebastian.bathke Sebastian Bathke
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce