Skip to content

Updating schedule on a container does not change it in the service #1

@smazurov

Description

@smazurov

Description

When you change schedule on your cron container, instead of assigning it for the first time, it gets picked up, but because uuid does not change (i thought it would!), it does not update the schedule at which it runs in the cron service.

Steps to reproduce

  1. Assuming cron is running (in debug mode) and has registered a scheduled container
  2. Go to service with scheduled container and change the schedule to be more or less frequent
  3. See that new schedule is displayed, but not reflected in the schedule that actually runs

What should happen

Cron service should pick up new schedule, check to see if its the same as old, if not, mark the current cron job as "stale" and add a new one for new schedule

Workaround

Restart cron service.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions