Skip to content

Conversation

@ewels
Copy link
Member

@ewels ewels commented Dec 17, 2025

Summary

Enhances the Poll files node with improved output configuration and deleted file detection:

  • Added pollIntervalSeconds field to output payload alongside nextPoll for easier interval tracking
  • Made the "All results" output hidden by default with a checkbox option to enable it (reduces noise for most use cases)
  • Added new "Deleted results" output that fires when files are removed from the Data Link

Details

New pollIntervalSeconds field

The "All results" output now includes msg.payload.pollIntervalSeconds (in seconds) alongside the existing msg.payload.nextPoll timestamp, making it easier for downstream nodes to understand the polling schedule.

Configurable "All results" output

The output that fires on every poll is now disabled by default. Most users only need the "New results" output, so this reduces clutter. Enable via the new "Output all results on every poll" checkbox.

Deleted files detection

New output that fires when files are removed from the Data Link between polls. This enables workflows that need to react to file deletions (e.g., cleanup tasks, audit logging).

Output configuration:

  • Default (2 outputs): New results, Deleted results
  • With checkbox enabled (3 outputs): All results, New results, Deleted results

Test plan

  • Deploy a Poll files node and verify it has 2 outputs by default (New, Deleted)
  • Enable "Output all results on every poll" and verify 3 outputs appear (All, New, Deleted)
  • Add a file to the Data Link and verify the "New results" output fires
  • Delete a file from the Data Link and verify the "Deleted results" output fires
  • Verify pollIntervalSeconds is present in the "All results" payload when enabled

🤖 Generated with Claude Code

ewels and others added 3 commits December 16, 2025 17:07
Add a new field to the "All results" output payload that reports the
poll interval duration in seconds, alongside the existing nextPoll
timestamp. This makes it easier for downstream nodes to understand the
polling schedule.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
Make it a config option to include it again.
Hoping to avoid people connecting it to stuff without reading the docs.
@github-actions
Copy link

github-actions bot commented Dec 17, 2025

🐳 Docker PR Build

Status ❌ Build failed
Commit 4045b78a573fed13e9cb8d821f82190b16d67183

One or more Docker image builds failed. Check the workflow logs for details.

View workflow run

ewels and others added 8 commits December 18, 2025 09:35
Tests were written for upstream's 2-output structure (All, New) but
the current implementation uses outputAllPolls to control outputs:
- Default: 2 outputs (New, Deleted)
- outputAllPolls=true: 3 outputs (All, New, Deleted)

Updated 7 tests to use outputAllPolls: true and 3-output wire config.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@ewels ewels merged commit baf8329 into main Dec 18, 2025
6 of 8 checks passed
@ewels ewels deleted the poll-files-tweaks branch December 18, 2025 16:46
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.

2 participants