Limits, Rate Behavior, And Operational Constraints

Version 1.9.3

AreaObserved behaviorDeveloper guidance
Ticket bulk actionsALSP_Model_Tickets_Bulk::MAX_TICKETS is 100.Chunk bulk automation into 100-ticket batches or smaller.
ChatbotRate limiter uses per-user or per-IP transients when enabled. Defaults in source are 20 free requests, 100 paid requests, and 60 minutes per window.Treat chatbot calls as limited and show retry feedback from responses.
REST APINo global numeric REST rate limit is defined in the router.Add your own throttling for public custom endpoints.
Email providersProvider-specific Gmail, Microsoft, and IMAP limits are not codified as stable numeric limits.Expect provider throttling and make import jobs idempotent.
Cron processingMail queue, cleanup, attention, trash, and email import depend on WordPress scheduled events.Do not assume immediate execution; design retries safely.
Privacy erasureAwedesk redacts retained support history instead of deleting all operational tickets.Extensions storing personal support data should join the privacy inventory and implement export/erase behavior.
Guest accessGuest support flows depend on admin settings and endpoint permission logic.Check both signed-in and signed-out behavior for extensions.