Skip to content

Operators claim unfiltered workflow instances when selectors are configured #527

@cdavernas

Description

@cdavernas

I tried this:

Configured an operator with label selectors to limit which workflow instances it should claim. I expected the operator to only pick up instances of workflows that matched those selectors.

This happened:

The operator still claimed and executed workflow instances that did not match its configured selectors. It ignored the filtering logic entirely, resulting in unexpected execution behavior.

I expected this:

The operator to only claim workflow instances that match its configured selectors, and ignore all others.

Is there a workaround?

No response

Anything else?

Issue raised by @ericlacher in #515 (comment).

Again, thanks @ericlacher ❤️

Platform(s)

No response

Community Notes

  • Please vote by adding a 👍 reaction to the issue to help us prioritize.
  • If you are interested to work on this issue, please leave a comment.name: Bug Report 🐞

Metadata

Metadata

Assignees

Labels

app: operatorConcerns the Operatorpriority: highIndicates a high priority issuetype: bugSomething isn't workingweight: 1An issue that has a very low development impact

Type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy