Keep Axis unlimited actions bound to a stateful condition

Bottom line: Describe both the event that starts the action and the state that should keep it running. Reject a proposed unlimited rule when that continuing condition has not been identified and checked.

Source fact: documented behavior

Axis’s Event and action services requires an unlimited action to have at least one condition, while allowing its start event to be omitted.

The primary action starts when its start event occurs and all configured conditions hold; the source says the action stops when any condition ceases to hold.

Each condition must identify one stateful event; a filter matching no stateful event or several such events causes AddActionRule to fail with InvalidconditionFilterFault.

What the source does not establish

Do not infer a complete action rule from an event name or a successful template lookup. Confirm the actual product’s supported events and action templates. Keep the rule’s lifetime separate from a guarantee about physical output, recording continuity or emergency response.

Applicability questions

• What approved action should start, and what should make it stop?
• Which actual stateful event supplies each continuing condition?
• Does each condition filter identify exactly the intended event?
• Who observes the action and can stop the isolated exercise?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends reviewing a rule’s start event and continuing conditions as separate entries before enabling an unlimited action.

1. Write a proposed harmless case in which a test indicator should operate only while an approved sensor state is active. Name the required start behavior and end behavior separately. Obtain the actual event declaration and action template from the supported device rather than copying the documentation’s demonstration identifiers.
2. Review every condition expression against that declaration. Ask a second reviewer to identify the single stateful event it selects and explain the intended active value. Keep a pulse used as a start event out of the continuing-condition column. Resolve an empty or ambiguous match before creating the operational rule.
3. Create only the authorized isolated rule through the documented workflow and retain the returned result. Observe the proposed active-state case, then return the test input to its approved inactive state. Require an independent observation of the output ending. Remove the temporary rule through its supported process and reconcile the retained production configuration.

Verification and evidence

Retain the rule definition, supported event declaration, action identity, condition filters and sanitized creation outcome. Record the actual input transitions and observed action alongside the planned lifetime. Keep a rejected rule as a configuration finding instead of repeatedly broadening its filter until it saves.

For a proposed desk exercise, present one missing condition and one expression that selects several stateful events. Have the reviewer identify why each is unsuitable before any device change. The exercise is a planning proposal; no action rule was created, physical output operated or response time measured for this article.

Official references

• Event and action services — Axis Communications; official VAPIX documentation.

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.