Please add a column that shows the next time a host is going to run a check for updates

[begunfx]

This is my watcher screen. It does show the cron schedule for all of my servers. I would love it if there was an additional column that would provide the next time that host will execute a check for updates.

This would give me quick visiblity when I can expect the next check to run for each server. Thanks!

[s-b-e-n-s-o-n]

This is coming in the next RC.

The watcher API and UI now expose next run metadata — you'll see when each host is scheduled to run its next update check. This is surfaced in the Agents view so you can see at a glance when each watcher will next poll for updates (6706929e).

The next RC will be out shortly — let us know if the display format works for your use case or if you'd like it presented differently.

[begunfx]

Seeing this now. Great improvement. Love the visibility to know when my containers will be checked next. Question: Does it make more sense to have a countdown to the next scan OR the local timestamp as to when that scan will initiate? I see a benefit to either or. A third option might be a configurable preference to show either time remaining Or timestamp.

This is what it currently looks like for me:

Thoughts?

[s-b-e-n-s-o-n]

Good question — both framings are genuinely useful, and which one wins depends on what you're doing at the moment:

• Relative ("in 14m") wins for at-a-glance scanning — you don't have to do mental arithmetic against the current time.
• Absolute ("14:32") wins when you're correlating against logs, backups, or other scheduled work.

The plan is to give you both in one cell: render the relative countdown as the primary value (updating live) with the absolute local timestamp in the tooltip/title attribute on hover. That's the same pattern we already use for Last seen and Created elsewhere in the UI, so it'll feel consistent.

A user-configurable "swap primary/secondary" preference is cheap to add on top of that later if the default doesn't land well for enough users, but I'd rather ship the dual-display first and let real usage tell us whether the preference is needed.

Leaving this open to track the dual-display + hover tooltip work. Thanks for pushing on the format — the current static timestamp was the minimum viable version, this is the real thing.

[s-b-e-n-s-o-n]

Quick update — the dual-display is built and lands in the next release. The cell now shows the relative countdown as the primary value, with the absolute local timestamp on hover (same pattern we use for Last seen / Created), so you get both framings in one place without a preference toggle.

Should be in v1.5.0-rc.10 when it cuts shortly — give it a try and let me know if the tooltip format lands right, or if the countdown cadence (e.g. live update vs. refresh on poll) needs tweaking.

[begunfx]

Seeing this in rc10. I think this behavior works. Thanks! I think you can probably close this.

[s-b-e-n-s-o-n]

Glad it lands well — closing as resolved. Feel free to reopen or file a new discussion if the countdown cadence or tooltip format ever feels off in practice.