Update liveness trigger docs: no cooldown for part online/offline#5195
Merged
btshrewsbury-viam merged 2 commits intoJul 14, 2026
Conversation
Part online and part offline triggers now fire on every state transition with no cooldown interval. The ENABLE_LIVENESS_TRIGGER_- STATE_TRANSITION_NOTIFICATIONS feature flag was removed (app#12683), making event-based liveness notifications the default behavior. Updated four pages to remove seconds_between_notifications from liveness trigger examples and add notes explaining that these triggers fire on every transition. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01PLP3YPPgRvxxiFZHrtWE1d
✅ Deploy Preview for viam-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
viambot
added
the
safe to build
Collaborator
|
Marvin (@enternal-L) Would you mind reviewing this please? |
Marvin (enternal-L)
approved these changes
Jul 14, 2026
|
🔎💬 Inkeep AI search and chat service is syncing content for source 'Viam Docs' |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part online and part offline triggers now fire on every state transition with no cooldown interval. The
ENABLE_LIVENESS_TRIGGER_STATE_TRANSITION_NOTIFICATIONSfeature flag was removed in app#12683, making event-based liveness notifications the default behavior.Source changes
ENABLE_LIVENESS_TRIGGER_STATE_TRANSITION_NOTIFICATIONSfeature flag — liveness triggers are now always event-based with no cooldownDocs changes
docs/reference/triggers.md: Removedseconds_between_notificationsfrom the part status trigger template; added note that part status triggers fire on every state transition. Updated the attributes table to note the field is ignored forpart_onlineandpart_offline.docs/monitor/alert.md: Removedseconds_between_notificationsfrom part online and part offline JSON examples; removed "set the alert frequency" from builder mode instructions (the UI hides the cooldown field for liveness triggers); updated "Manage alert frequency" section to clarify it applies to data triggers, not liveness triggers.docs/data/trigger-on-data.md: Updated the notification interval section to noteseconds_between_notificationsis ignored for liveness triggers.docs/cli/reference.md: Addedpart_offlineto the event type list; removedseconds_between_notificationsfrom thepart_onlineCLI example.How I found these
seconds_between_notifications,part_online,part_offline,liveness,cooldown, andstate transitionacross the entire docs repo. Found references in 5 files; 4 required updates.Generated by daily docs change agent
Generated by Claude Code