Decision: default content-verification polling interval (Q2) #59

Closed
opened 2026-11-07 18:58:25 +00:00 by vivy · 2 comments
Owner

What

Open question Q2. Assumption: 15 minutes.

Done when

Default chosen and recorded.

Plan

plan/open-questions.md#q2

Status

Product owner decision.


Routing/Hold: no agent is routed to this issue automatically. To take it yourself, assign yourself. Vivy removes the hold when it is handed to an agent.
Created for GRI-1818 from plan/overview/roadmap.md and the MVP plan on GRI-1761.

## What Open question Q2. Assumption: 15 minutes. ## Done when Default chosen and recorded. ## Plan plan/open-questions.md#q2 ## Status Product owner decision. --- `Routing/Hold`: no agent is routed to this issue automatically. To take it yourself, assign yourself. Vivy removes the hold when it is handed to an agent. Created for GRI-1818 from `plan/overview/roadmap.md` and the MVP plan on GRI-1761.
Owner

lets make it default every 15minutes. But configurable in the settings and if the client is connect with a web-socket. It only checks after reconnecting. Because the server will push it over the web-socket.

and the check happens on the client to the server. Not server to client. For safety and for management is easier (less open ports, no static ips needed for the clients, ....)

lets make it default every 15minutes. But configurable in the settings and if the client is connect with a web-socket. It only checks after reconnecting. Because the server will push it over the web-socket. and the check happens on the client to the server. Not server to client. For safety and for management is easier (less open ports, no static ips needed for the clients, ....)
Author
Owner

Recorded in PR #72. My reading: the client checks every 15 min only while the WebSocket is down (each attempt is a reconnect), and once on every reconnect; no periodic check while connected. The accepted limit: a push the client received but failed to apply is caught only at the next reconnect, so the client must report a failed apply as an error itself. Say so if you meant otherwise.

Recorded in PR #72. My reading: the client checks every 15 min only while the WebSocket is down (each attempt is a reconnect), and once on every reconnect; no periodic check while connected. The accepted limit: a push the client received but failed to apply is caught only at the next reconnect, so the client must report a failed apply as an error itself. Say so if you meant otherwise.
vivy closed this issue 2026-11-07 20:04:07 +00:00
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoire-of-digital-signage#59
No description provided.