ApplicationSet List Generator in ArgoCD v2.8: Unclear Prune Propagation When Multiple Generators Overlap

Goal

Determine how the prune flag behaves when multiple ApplicationSet objects, each using the new List generator in ArgoCD v2.8, reference the same Git repository and produce overlapping resources.

Constraints & Uncertainty

• ArgoCD v2.8 with the List generator processes entries sequentially.
• Multiple ApplicationSets may generate identical manifests.
• The documentation notes unpredictable pruning when overlapping resources exist, but does not specify the order or propagation policy.
• Concurrent syncs can trigger race conditions in the repo server.

Specific Questions

1. When two List generators create identical resources, does the prune flag applied to one ApplicationSet propagate to the other, and if so, in what order are resources deleted?
2. Is there a documented mechanism to enforce deterministic pruning across overlapping ApplicationSets in v2.8?
3. What observable events or logs indicate that a race condition occurred during concurrent syncs of List-generated applications?