[GH-ISSUE #399] Add Option to Purge All Redis Queues per Server or Entire Team Server #258

New issue

Closed

opened 2026-03-03 11:14:21 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 11:14:21 +03:00

Owner

Originally created by @charanm927 on GitHub (Aug 12, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/399

Originally assigned to: @manikanta9176 on GitHub.

Description:

Introduce functionality in dFlow that allows users to purge all Redis queues either for:

A specific server, or
All servers within a team.

This should give users more control over their environments and help in clearing stuck jobs, failed tasks, or outdated data without manual Redis intervention.

Acceptance Criteria:

Add purge option in the server settings.
Add purge option in the team-level settings for all servers.
Prompt confirmation before execution to prevent accidental data loss.
Log purge actions for audit purposes.
Ensure operation is fast and does not disrupt other running services unnecessarily.

Benefits:

Simplifies queue management for users.
Quickly resolves issues caused by stuck or corrupted jobs.
Reduces reliance on manual Redis commands.

Originally created by @charanm927 on GitHub (Aug 12, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/399 Originally assigned to: @manikanta9176 on GitHub. **Description:** Introduce functionality in dFlow that allows users to purge all Redis queues either for: - A specific server, or - All servers within a team. This should give users more control over their environments and help in clearing stuck jobs, failed tasks, or outdated data without manual Redis intervention. **Acceptance Criteria:** - Add purge option in the server settings. - Add purge option in the team-level settings for all servers. - Prompt confirmation before execution to prevent accidental data loss. - Log purge actions for audit purposes. - Ensure operation is fast and does not disrupt other running services unnecessarily. **Benefits:** - Simplifies queue management for users. - Quickly resolves issues caused by stuck or corrupted jobs. - Reduces reliance on manual Redis commands.