{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/keep-axis-unlimited-actions-bound-to-a-stateful-condition/", "item": { "id": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/", "slug": "keep-axis-unlimited-actions-bound-to-a-stateful-condition", "url": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition.md", "json": "https://update.dsesecurity.com/api/v1/posts/keep-axis-unlimited-actions-bound-to-a-stateful-condition/" }, "title": "Keep Axis unlimited actions bound to a stateful condition", "summary": "Check that an Axis unlimited action has a valid stateful condition. Keep a start-event pulse separate from the condition that bounds how long the action should run.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-29T20:33:30+00:00", "modified_at": "2026-10-29T20:33:34+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 510, "potentially_affected": "Axis products exposing the documented Event and action services interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends reviewing a rule’s start event and continuing conditions as separate entries before enabling an unlimited action.", "primary_source": { "name": "Axis Communications — Event and action services", "url": "https://developer.axis.com/vapix/network-video/event-and-action-services/", "published_on": null, "authority": "Axis Communications" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

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.

\n

Source fact: documented behavior

\n

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

\n

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.

\n

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

\n

What the source does not establish

\n

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.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

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

\n

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

\n
    \n
  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. \n
  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. \n
  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.
    4. \n
\n

Verification and evidence

\n

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.

\n

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.

\n

Official references

\n\n

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

\n", "content_text": "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.\nSource fact: documented behavior\nAxis’s Event and action services requires an unlimited action to have at least one condition, while allowing its start event to be omitted.\nThe 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.\nEach condition must identify one stateful event; a filter matching no stateful event or several such events causes AddActionRule to fail with InvalidconditionFilterFault.\nWhat the source does not establish\nDo 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.\nApplicability questions\n\nWhat approved action should start, and what should make it stop?\nWhich actual stateful event supplies each continuing condition?\nDoes each condition filter identify exactly the intended event?\nWho observes the action and can stop the isolated exercise?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends reviewing a rule’s start event and continuing conditions as separate entries before enabling an unlimited action.\n\nWrite 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.\nReview 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.\nCreate 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.\n\nVerification and evidence\nRetain 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.\nFor 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.\nOfficial references\n\nEvent and action services — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "content_markdown": "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.\n\n## Source fact: documented behavior\n\nAxis’s [Event and action services](https://developer.axis.com/vapix/network-video/event-and-action-services/) requires an unlimited action to have at least one condition, while allowing its start event to be omitted.\n\nThe 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.\n\nEach condition must identify one stateful event; a filter matching no stateful event or several such events causes AddActionRule to fail with InvalidconditionFilterFault.\n\n## What the source does not establish\n\nDo 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.\n\n## Applicability questions\n\n- What approved action should start, and what should make it stop?\n\n- Which actual stateful event supplies each continuing condition?\n\n- Does each condition filter identify exactly the intended event?\n\n- Who observes the action and can stop the isolated exercise?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends reviewing a rule’s start event and continuing conditions as separate entries before enabling an unlimited action.\n\n- 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.\n\n- 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.\n\n- 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.\n\n## Verification and evidence\n\nRetain 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.\n\nFor 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.\n\n## Official references\n\n- [Event and action services](https://developer.axis.com/vapix/network-video/event-and-action-services/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/", "url": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "IT", "item": "https://update.dsesecurity.com/topic/it/" }, { "@type": "ListItem", "position": 3, "name": "Keep Axis unlimited actions bound to a stateful condition", "item": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/#article", "identifier": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/", "url": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/", "headline": "Keep Axis unlimited actions bound to a stateful condition", "description": "Check that an Axis unlimited action has a valid stateful condition. Keep a start-event pulse separate from the condition that bounds how long the action…", "abstract": "Check that an Axis unlimited action has a valid stateful condition. Keep a start-event pulse separate from the condition that bounds how long the action should run.", "articleBody": "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.\nSource fact: documented behavior\nAxis’s Event and action services requires an unlimited action to have at least one condition, while allowing its start event to be omitted.\nThe 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.\nEach condition must identify one stateful event; a filter matching no stateful event or several such events causes AddActionRule to fail with InvalidconditionFilterFault.\nWhat the source does not establish\nDo 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.\nApplicability questions\n\nWhat approved action should start, and what should make it stop?\nWhich actual stateful event supplies each continuing condition?\nDoes each condition filter identify exactly the intended event?\nWho observes the action and can stop the isolated exercise?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends reviewing a rule’s start event and continuing conditions as separate entries before enabling an unlimited action.\n\nWrite 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.\nReview 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.\nCreate 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.\n\nVerification and evidence\nRetain 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.\nFor 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.\nOfficial references\n\nEvent and action services — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "datePublished": "2026-10-29T20:33:30+00:00", "dateModified": "2026-10-29T20:33:34+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/keep-axis-unlimited-actions-bound-to-a-stateful-condition/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Keep Axis unlimited actions bound to a stateful condition" }, "articleSection": [ "IT", "Video Surveillance" ], "keywords": [ "IT", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 510, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Axis Communications — Event and action services", "url": "https://developer.axis.com/vapix/network-video/event-and-action-services/" } } ] } }