Details
Description
Currently services that fail provisioning may continue to attempt provisioning every time the cron runs, indefinitely.
A setting should be added "Halt Automatic Provision After Attempts" which will stop provision attempts on a service after X attempts have failed. The setting should be a drop down containing
- Never
- 1
- 2
- ...
- 30
In order to track number of failed attempts we should add a new status to the log_services table called provision_failed. Make sure that adding this status does not mess up any of the current suspension/unsuspension behavior that depends on this log.
In addition, a new email template service_provision_halted should be created with the name Service Provisioning Halted and the subject Automatic Provisioning Halted for Service -
{service.name}This email should be sent to subscribed admins when provisioning is halted on a service. This email should appear under the "Email Subscription Notices" section on the My Info and Staff Group pages.
For additional visibility, we may want to add a note to the clients dashboard, similar the the due invoices notice, that tells them which services, if any, have halted provisioning.
Issue Links
- relates to
-
CORE-901
Add service action backoff after failure
-
- Closed
-
Activity
If we do this task it would make at least part of CORE-901 unnecessary
Instead of using log_services we should generalize service_invoices
This task will work similar to the service renewal queue. We'll rename Tools > Renewal Queue, so that it works for both new and renewing services, and we will show whether it's a new or renewing service in the queue.
Paul Phillips
added a comment - This task will work similar to the service renewal queue. We'll rename Tools > Renewal Queue, so that it works for both new and renewing services, and we will show whether it's a new or renewing service in the queue. 
We also may want to do this sort of thing for suspension/unsuspension/cancellation and not just for service creation