[GH-ISSUE #53] [Feature]: NON Scheduled Queue #19

New issue

Closed

opened 2026-05-07 00:05:15 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:05:15 +02:00

Owner

Originally created by @pinionless on GitHub (Jan 3, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/53

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

Current Limitation: Currently, the system requires a scheduled start time or immediate execution when adding sliced files to the workflow. There is no native way to "stage" or "buffer" tasks that are ready for processing but shouldn't necessarily run right away.

The Pain Point: This creates a bottleneck for users who prepare multiple files in advance but want to manage system resources or manual oversight by triggering the jobs manually at a later time.

Proposed Solution

Queued but Unscheduled" State I propose adding a "Queue Only" option for sliced files. This would allow a task to be added to the processing queue without an assigned start date or time.

Key Functional Requirements:

Manual Trigger: Tasks in this state should remain idle until the user explicitly clicks a "Start" or "Release" button.

Status Label: A specific UI indicator (e.g., Status: Pending or Status: Staged) to distinguish these from active or failed tasks.

Alternatives Considered

No response

Feature Category

Print Queue & Scheduling

Priority

Critical for my use case

Mockups or Examples

No response

Contribution

I would be willing to help implement this feature

Checklist

I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @pinionless on GitHub (Jan 3, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/53 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case Current Limitation: Currently, the system requires a scheduled start time or immediate execution when adding sliced files to the workflow. There is no native way to "stage" or "buffer" tasks that are ready for processing but shouldn't necessarily run right away. The Pain Point: This creates a bottleneck for users who prepare multiple files in advance but want to manage system resources or manual oversight by triggering the jobs manually at a later time. ### Proposed Solution Queued but Unscheduled" State I propose adding a "Queue Only" option for sliced files. This would allow a task to be added to the processing queue without an assigned start date or time. Key Functional Requirements: Manual Trigger: Tasks in this state should remain idle until the user explicitly clicks a "Start" or "Release" button. Status Label: A specific UI indicator (e.g., Status: Pending or Status: Staged) to distinguish these from active or failed tasks. ### Alternatives Considered _No response_ ### Feature Category Print Queue & Scheduling ### Priority Critical for my use case ### Mockups or Examples _No response_ ### Contribution - [ ] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested

BreizhHardware

2026-05-07 00:05:15 +02:00

closed this issue
added the
enhancement
label

BreizhHardware commented

2026-05-07 00:05:16 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 4, 2026):

Here you go.....

Please use branch 0.1.6b6 and let me know if that works for you.

@maziggy commented on GitHub (Jan 4, 2026): Here you go..... Please use branch 0.1.6b6 and let me know if that works for you. <img width="472" height="568" alt="Image" src="https://github.com/user-attachments/assets/b0946a95-a2a6-43a7-8141-17356b8bf4e4" /> <img width="1794" height="197" alt="Image" src="https://github.com/user-attachments/assets/2e712825-9186-4b6b-9699-d12728f7e2eb" />

BreizhHardware commented

2026-05-07 00:05:16 +02:00

Author

Owner

@pinionless commented on GitHub (Jan 4, 2026):

Works perfectly. Thanks!

@pinionless commented on GitHub (Jan 4, 2026): Works perfectly. Thanks!

BreizhHardware referenced this issue

2026-05-07 00:14:55 +02:00

[PR #19] [MERGED] 0.1.5b6 #906