2026-10-02

Hub API

• Added support for deployment-managed global workflows alongside organization-specific custom workflows, with consistent workflow resolution and launch behavior
• Introduced advanced automatic workflow Start edge behavior, enabling per-edge trigger conditions, schedules, scopes, and classification-based activation
• Improved workflow run compatibility by supporting both legacy and consolidated stage execution formats in API responses
• Added incremental marker synchronization support with cursor-based updates and watermark tracking for more efficient client syncing
• Improved privacy enforcement for custom alerts by returning explicit permission-denied responses when restricted alert types are used
• Fixed face redaction submissions to correctly handle media proxy URLs, improving reliability for proxied media workflows

Hub Workflows

• Added support for advanced workflow trigger routing with scoped schedules, conditional entry paths, and classifier-aware activation rules
• Workflow runs now use immutable execution snapshots, ensuring in-progress runs continue with their original routing and stage configuration even after workflow edits or redeployments
• Improved workflow reliability by preserving active runs across disabled or updated workflow definitions and retrying failed dispatch scenarios safely
• Added richer workflow execution tracking, including detailed dispatch and resolution timing for each stage
• Workflow timestamps now support millisecond precision for more accurate execution and finalization tracking
• Improved conditional workflow evaluation with support for nested logical conditions and expanded matching behavior
• Added configurable operation-to-queue routing through WORKFLOW_STAGE_QUEUES for deployments without direct config workflow references
• Enhanced workflow identity handling so workflows can retain stable IDs across renames and configuration changes
• Strengthened workflow security by preventing tenant-authored workflows from overriding deployment queue and worker routing settings

Hub Vlm

• Recording descriptions now use activity-focused summaries that describe what happens in the video instead of repeating static scene details
• Quiet or unchanged recordings no longer overwrite existing descriptions with redundant scene summaries
• Improved handling of generated summaries to avoid duplicate or repetitive descriptions by falling back to distinct observation sentences when needed
• Enhanced scene metadata quality by preserving longer descriptive phrases for locations, objects, zones, and lighting details
• Expanded analysis output to separately track activity summaries and stable scene context for clearer video understanding

Hub Frontend

• Added a new “With analysis” media filter to quickly find recordings that include detections, markers, descriptions, or other analysis results
• Improved live timeline updates so new and updated markers appear faster and more reliably without requiring full timeline reloads
• Enhanced alert management with support for private alerts, including clearer visibility indicators and preserved privacy settings
• Refreshed the alert audit log experience with improved filtering, search, clearer event details, and one-click filter reset
• Added confirmation prompts for account and alert deletion actions to help prevent accidental removals
• Improved site list sorting for more intuitive alphanumeric ordering in account management views
• Improved handling of runtime feature flag values for more consistent environment configuration behavior

Pipeline Analysis

• Improved reliability of regenerated thumbnail processing by routing jobs through the correct FIFO queue to preserve processing order
• Fixed an issue where thumbnail regeneration events could be sent to the wrong queue, reducing the risk of missed or out-of-order thumbnail updates

Learn

• Added support for external workflow stages, allowing customer-managed services to connect to Hub workflows through secure RabbitMQ or HTTPS integrations with authenticated callbacks
• Expanded workflow documentation with guidance for running custom processing stages outside the Hub deployment while keeping internal credentials and routing protected
• Improved Live View device status indicators with clearer motion event badges and updated recording-state overlay behavior documentation
• Added release documentation covering recent improvements to workflows, media playback, analytics, Vault integrations, audit services, and VLM-powered scene understanding features

Website

Massage itself is not a proven way to reliably induce labor, but some types of massage may help relaxation, reduce stress, ease discomfort, and possibly support the body as labor approaches.

A few important distinctions matter:

• General prenatal massage is usually considered safe in a healthy pregnancy when done by someone trained in pregnancy massage.
• There’s limited evidence that stimulating certain pressure points (sometimes discussed in acupressure) can trigger contractions, but studies are mixed and effects are generally not strong or predictable.
• Deep abdominal massage, intense pressure, or aggressive techniques should be avoided during pregnancy.
• If someone is high-risk, has bleeding, preterm contractions, placenta issues, high blood pressure, or has been told to avoid certain activities, they should check with their clinician before getting a massage.

At full term, a massage might coincide with labor starting naturally, but that doesn’t mean it directly caused labor. If the goal is labor induction, it’s best to discuss safe options with an OB-GYN or midwife.

Helm Charts

• Added support for customizing workflow editor stages through new Hub configuration options
• Improved workflow queue handling to better separate workflow-specific queues from service queues
• Clarified workflow engine behavior for empty stage configurations, improving configuration consistency and predictability