Any Scheduler (All-In-One):
DynamicAnyScheduler is an all-in-one way to use compatible scheduler nodes in a custom sampling workflow. Instead of placing a different scheduler node each time you want to try one, you choose from the schedulers made available through this node. It then runs the chosen scheduler and passes along its result. This makes it easier to compare scheduling approaches while keeping the surrounding workflow in place. The available choices depend on the scheduler nodes installed in your ComfyUI environment and whether their outputs match this node’s required output type.
Any Scheduler (All-In-One) Input Parameters:
selection
This required dynamic selection lets you choose a compatible scheduler. Once you choose one, the selection also presents that scheduler’s own settings, which control how it produces its schedule. Changing the choice can therefore change both the settings you see and the resulting schedule. The node considers registered nodes whose names contain Scheduler and whose single output matches its SIGMAS output type; it excludes nodes marked as all-in-one nodes. There is no fixed list of options in the provided source, and no minimum, maximum, or default value is specified for selection. Any settings displayed within a particular choice come from that scheduler, so their defaults and ranges cannot be stated here.
Any Scheduler (All-In-One) Output Parameters:
sigmas
The sigmas output is the SIGMAS value returned by the scheduler you chose. It represents the schedule of noise levels used during sampling: the scheduler determines those values, and this node passes its result through. Connect it to a compatible custom sampler input. The provided source does not specify the number of values or their exact progression, because those details depend on the selected scheduler and its settings.
Any Scheduler (All-In-One) Usage Tips:
- Connect
sigmasto a custom sampler that accepts aSIGMASschedule, then choose a scheduler from the availableselectionoptions. - To compare schedules, keep the rest of your workflow unchanged and switch the scheduler choice. Adjust any settings revealed by that choice according to the task and the scheduler’s own documentation.
- If an expected scheduler is missing, check that it is installed and registered, its registered name contains
Scheduler, and it has exactly one compatibleSIGMASoutput. The provided source defines no setting that forces an incompatible node into the list.
Any Scheduler (All-In-One) Common Errors and Solutions:
No scheduler options appear
- Explanation: The node found no registered scheduler that passed its name and output checks. This is a possible interface state, not an error message defined in the provided source.
- Solution: Check that your scheduler nodes are installed and loaded. Confirm that a candidate’s registered name contains
Schedulerand that it produces exactly one compatibleSIGMASoutput.
KeyError: 'selection'
- Explanation: At execution, the node expects the chosen value to contain a
selectionentry identifying the scheduler. This error can occur if that entry is absent. - Solution: Reopen the node, choose an available scheduler again, and rerun the workflow. If it persists, recreate the node to refresh its dynamic selection.
KeyError: '<scheduler name>'
- Explanation: The node looks up the chosen scheduler in the current node registry. A lookup error can occur if that scheduler is no longer registered under the saved name.
- Solution: Check that the scheduler node is still installed and loading correctly, then choose it again from the current options.
Unexpected keyword argument or missing required argument
- Explanation: The chosen scheduler receives the settings supplied through the dynamic selection. A parameter error can occur if those settings no longer match the scheduler’s execution method, for example after its implementation changes. The exact message depends on that scheduler.
- Solution: Reselect the scheduler to refresh its settings and check that its required values are present. If the error continues, consult the selected scheduler’s documentation or report the mismatch to its maintainer.
A selected scheduler reports its own execution error
- Explanation: This node calls the chosen scheduler directly, so errors raised by that scheduler can appear while this node runs. Their messages and causes depend on the scheduler and are not defined in the provided source.
- Solution: Note which scheduler is selected, review the settings shown for it, and troubleshoot the reported message using that scheduler’s documentation.
