SETUP
1. Drag one "Idle Timer" element onto the page. It is a 1x1 utility element and renders nothing.
2. IMPORTANT: leave "This element is visible on page load" CHECKED, unchecking it stops the timer from ever starting. The element hides its own pixels and disables pointer events, so it will not appear or block clicks.
3. Set "Idle seconds" to how many seconds of inactivity should count as idle (for example 300 for five minutes).
4. Leave "Enabled" as yes. Set it to a dynamic expression if you want to switch the timer off, for example only run it when the user is logged in.

FIELDS

- Idle seconds (number): seconds of inactivity before the idle event fires. A zero, negative, blank, or invalid value disables the countdown until a valid positive value is supplied.
- Enabled (yes/no): turns the timer on or off. Turning it off clears the countdown and resets the states.

EVENTS

- User became idle: fires once when the inactivity threshold is reached. It will not fire again until the user becomes active and then goes idle again.
- User became active: fires when any activity is detected after an idle period.

EXPOSED STATES

- Is idle (yes/no): whether the user is currently idle.
- Idle for seconds (number): seconds since the last activity. Refreshed once per second and keeps counting up after the idle event, like an inactivity chronometer. Resets to 0 on any activity.
- Last activity (date): timestamp of the most recent detected activity.

ELEMENT ACTION

- Reset idle timer: restarts the countdown from zero and, if the user was idle, transitions the element back to active. Useful after the user confirms a "still there?" popup.

TYPICAL USE

Create a workflow on "When Idle Timer's User became idle" and add your actions, such as showing a warning group, logging the user out, or creating a log entry. Optionally add a "User became active" workflow to hide the warning again. To display a countdown, bind a text to Idle Timer's Idle for seconds.

IMPORTANT LIMITATIONS

- A browser cannot read operating-system-wide idle time. This element only detects inactivity directed at the Bubble page: keyboard, pointer, touch, wheel, scroll, and focus. Working in another application will NOT reset the timer.
- Elapsed time is measured from timestamps, not a counter, so throttled or delayed browser timers do not lose time.
- Browsers may freeze a backgrounded tab. Elapsed wall-clock time still counts, but the workflow can only run once the browser lets the page's JavaScript resume.
- Use one instance per page. Multiple instances work, but each attaches its own listeners and keeps its own timer.