Feature request
Allow a caller to prevent equivalent work from being queued while an operation is already active.
Rationale
Some user actions and service commands should run at most once at a time. Queueing duplicates performs stale work later, while cancel-previous and shared-result behavior solve different problems.
Use case
A user invokes a sign-in or refresh command repeatedly while the first invocation is still running. The original operation should continue, and later duplicate invocations should not execute.
Desired behavior
- The active operation continues unchanged.
- Equivalent submissions made while it is active do not execute later.
- The submitting caller receives a clear, observable indication that its operation was not accepted.
- Once the active operation completes, a new submission can run normally.
- Cancellation and disposal retain their normal TaskFlow behavior.
Feature request
Allow a caller to prevent equivalent work from being queued while an operation is already active.
Rationale
Some user actions and service commands should run at most once at a time. Queueing duplicates performs stale work later, while cancel-previous and shared-result behavior solve different problems.
Use case
A user invokes a sign-in or refresh command repeatedly while the first invocation is still running. The original operation should continue, and later duplicate invocations should not execute.
Desired behavior