Skip to content

jobs should be deleted and recreated if new values are made #138

@orcutt989

Description

@orcutt989

We made changes to the rollup node values f58b3cf and the actdivation job did not clear out and restart causing us to manually have to delete and create a new job on the cluster.

Expected functionality should be if a job is dependent on a value it should be deleted and restarted to prevent this manual intervention.

Metadata

Metadata

Assignees

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