Allow for Axis tracking filters before expecting an event

Bottom line: Write the expected qualification delay before diagnosing a missing tracking event. Compare the permitted object’s actual movement with the configured filter and the event timeline, then inspect any required recording context separately.

Source fact: documented behavior

Axis’s Digital autotracking API says ignore-filter conditions must be evaluated and satisfied before tracking begins and an event is emitted.

For the short-lived-object Time filter, an object must still be moving after the configured interval; tracking and its event are delayed by that interval.

The page requires Digital Autotracking 2 or later for its short-lived-object filter and recommends recording pre-trigger coverage when a delayed event starts recording.

What the source does not establish

Do not infer equivalent filter behavior for a different analytics application or a guarantee that every moving object will qualify. Confirm application version, camera support and the exact configured areas and filters. A tracking event alone does not establish the required recorded lead-in, classification accuracy or complete detection coverage.

Applicability questions

• Does the actual application version support the configured filter?
• Which filter interval and scene region are being assessed?
• How long should each approved test object remain moving?
• What pre-event context must the recording owner be able to retrieve?

DSE recommendation: controlled next steps

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

DSE recommends comparing object motion, filter qualification, event time and retrieved recording context as separate evidence.

1. Read the actual application configuration and identify the supported short-lived-object filter and its value. Review the intended include and exclude areas with the operator. Write a proposed harmless short appearance and a longer permitted movement as distinct cases, choosing the paths and timing under the site’s approved test conditions rather than inventing a universal threshold.
2. Observe the two cases with authorized participants or harmless controlled inputs. Preserve the movement timeline and corresponding tracking-event observations. Keep the short case’s disposition separate from a communication failure. Investigate a longer qualifying-looking case with the actual configured filters and consumer evidence before disabling several nuisance controls together.
3. Where the event starts recording, have the recording owner review the supported pre-trigger setup against the required lead-in. Retrieve the relevant test interval through the normal authorized client and inspect the earlier movement independently. Leave insufficient context as a recording requirement to resolve rather than describing a later event bookmark as proof that the whole approach was retained.

Verification and evidence

Retain the application/version reference, areas, filter settings, proposed case definitions, actual motion and event timeline, and the permitted recording observation. Have a reviewer distinguish a configured qualification delay from an independently demonstrated message-path failure. Keep unexpected misses and nuisance events visible to the owner.

Use a proposed desk case where an investigator needs activity before the tracking event. Require an explicit pre-trigger and retrieval decision, without promising a fixed retention duration. No object was tracked, analytics accuracy measured or recording retrieved during preparation of this article.

Official references

• Digital autotracking API — 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.