You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Twilio status updating Celery job is querying the database for Notifications, and it is taking far too long to return results. See this example below where it took 12 seconds:
This query needs to be revisited to be more performant, possibly by:
Removing the ordering
Adding an index on some of the where conditions, sent_at and notification_status
Ticket is understood, and QA has been contacted (if the ticket has a QA label).
User Story(ies)
As a VANotify developer I want backend tasks to run as efficiently as possible So that resources have high availability
User Story - Business Need
The Twilio status updating Celery job is querying the database for Notifications, and it is taking far too long to return results. See this example below where it took 12 seconds:
This query needs to be revisited to be more performant, possibly by:
Removing the ordering
Adding an index on some of the where conditions,
sent_at
andnotification_status
Ticket is understood, and QA has been contacted (if the ticket has a QA label).
User Story(ies)
As a VANotify developer
I want backend tasks to run as efficiently as possible
So that resources have high availability
Additional Info and Resources
Acceptance Criteria
QA Considerations
Potential Dependencies
The text was updated successfully, but these errors were encountered: