SigniQ v1.4.20 – Release Notes
Date: 10‑09‑2026
This release includes a major architecture change to the scheduling system. We’ve tested it across all scheduling scenarios to ensure everything works smoothly. If you notice any timing issues or anything unusual, please reach out through our support chat — we’re here to help.
As part of expanding our booking capabilities, SigniQ will soon support event bookings and class bookings. These architecture changes ensure the system can scale for those new use cases while continuing to support all current booking flows correctly.
Scheduling Architecture Update
What changed
The scheduling and availability engine has been fully rearchitected. The previous cache relied on multiple interconnected cache instances, making it difficult to extend for upcoming event/class booking features.
The new system now uses:
- A tree‑structured model with node types (union, intersection, leaf, owner)
- A flat 60‑day booking store for fast availability generation
- A simplified and predictable availability calculation pipeline
Why it matters
This redesign makes the system more scalable, easier to maintain, and ready for advanced booking types — while keeping current scheduling behaviour stable and accurate.
New Notes Editor & User Section Redesign
What changed
A new notes editor has been added, and the entire user section in the admin panel has been rewritten.
Instead of only showing users who created accounts, the system now:
- Identifies users by email, phone, and date of birth
- Groups all bookings under those unified user entries
- Displays notes using the same identifiers
This solves the long‑standing issue where admin‑created bookings didn’t show proper user details.
Why it matters
Admins can now see complete booking history and notes for customers who never log in, making customer management far more accurate.
Admin tip: If the same admin email is used for multiple customers, the system will treat them as one person. Use correct customer details (or no email where appropriate) to keep records clean.
Normalized User Emails
What changed
User emails are now normalized before being stored or compared.
Why it matters
This prevents mismatches caused by formatting differences (capitalization, spacing), improving consistency in user identification and communication.
Retention State Editing Restrictions
What changed
Retention entries marked as completed or abandoned can no longer be edited.
Why it matters
This prevents accidental changes to finalized retention outcomes and keeps retention data reliable.
Booking Counter Reset Fix
What changed
A bug in the booking counter reset logic has been fixed. Previously, when customers fully used their booking limit, the counter didn’t reset correctly at the start of a new period.
Why it matters
Booking limits now reset accurately, avoiding situations where customers are incorrectly blocked or allowed beyond their limit.