Skip to content

Fix flushing when in variable delay mode#5382

Merged
knolleary merged 1 commit intomasterfrom
fix-delay-node-variable-mode-error
Jan 7, 2026
Merged

Fix flushing when in variable delay mode#5382
knolleary merged 1 commit intomasterfrom
fix-delay-node-variable-mode-error

Conversation

@dceejay
Copy link
Copy Markdown
Member

@dceejay dceejay commented Dec 12, 2025

to close #5381

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Proposed changes

This fixes the bug identified in #5381 where the delay node would send an extra unwanted message after the when flushing a message in variable delay mode. (Basically we weren't removing the fiush message itself from the queue if it was just a flush only message)

Checklist

  • I have read the contribution guidelines
  • For non-bugfix PRs, I have discussed this change on the forum/slack team.
  • I have run npm run test to verify the unit tests pass
  • I have added suitable unit tests to cover the new/changed functionality

@dceejay dceejay modified the milestone: 5.0 Dec 18, 2025
@knolleary knolleary merged commit bc4f5fe into master Jan 7, 2026
5 checks passed
@knolleary knolleary deleted the fix-delay-node-variable-mode-error branch January 7, 2026 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Delay node: flush=1 or flush=true creates an undefined message

2 participants