Known Issues & Limitations (v2.1)
We believe in transparent handover. The items below are known limitations of the current release and their planned resolutions.
Current Limitations
| Area | Limitation | Planned |
|---|---|---|
| SLA vs. calendar | SLA due dates use flat wall-clock hours (Critical 4h / High 8h / Medium 24h / Low 72h). The master calendar (working hours, weekends, holidays) is configurable but not yet applied to SLA/due-date maths | upcoming |
| Rate limiting | Self-serve organization registration is rate-limited per IP, but auth/webhook/general API endpoints are not yet | upcoming |
| Notification retry | Email/Teams delivery is fire-and-forget; transient failures are logged but not retried | upcoming |
| Attachment delete | Attachment-delete permissions exist but are granted to no default role — enable per-tenant from the role editor if needed | by design |
| Deletion | Deleting subjects/tickets/sub-tasks has no UI (mutations fail closed); comment deletion is own-comments-only | by design |
| Email app-only mode | The graph_app connection mode needs Mail.ReadWrite + Mail.Send application permissions with admin consent on the platform SSO app. Until those are granted, every app-only mail call returns 403. Use imap_oauth in the meantime | upcoming |
| IMAP basic auth | imap_basic does not work against Microsoft 365 — Microsoft retired basic auth for IMAP and SMTP AUTH. It remains for Gmail, Zoho, and on-prem hosts | by design |
| Email polling latency | Polled inboxes fetch on a 2-minute cycle, so a ticket can be up to ~2 minutes behind the email. Only graph_app is push | by design |
| Dead email columns | autoCreateTicket and the allow/block domain lists are no longer read by ingestion but still exist as columns, pending a cleanup migration | upcoming |
| Ticket editing | Edited via the details panel; no inline editing on the ticket list | by design |
| Commit id | Captured manually on the Dev Fixed → Review transition; there is no git integration to verify or link it | by design |
Environment Requirements
- Microsoft Teams sign-in requires accurate system clocks — clock skew greater than ~5 minutes can cause "Session Expired" errors (JWT
nbfvalidation). See Troubleshooting. - Modern browsers only (evergreen Chrome, Edge, Firefox, Safari).
Multi-tenancy notes
- A user who belongs to several tenants must select the right one in the tenant switcher; data never crosses tenants. Empty lists usually mean the wrong active tenant — see Troubleshooting.
- Tenants and memberships are suspended, never hard-deleted.
Reporting Issues
Report issues to your Analytics Aura support contact with: the page URL, your role, the organization (tenant), a screenshot, and the approximate time of the error.