Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-901

Add service action backoff after failure

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: Sponsored
    • Component/s: None
    • Labels:
      None

      Description

      If a service fails to provision, suspend, unsuspend, or cancel, it may be attempted as often as every 5 minutes, and would send an email to staff each time regarding the failure (This doesn't happen, there is no such email to staff).

      So we propose to create a setting that sets a service action backoff on failure, and sets a time interval for which not to attempt the action again. (Question: Where should this setting go?)

      Allow time intervals for waiting to attempt the action again:
      15 min, 30 min, 1 hour, ... 24 hours

      Edit: 2019/01/04

      In addition to this backoff feature, we should add:

      • A new email subscription notice under My Info for staff (including ACL to enable the option) that will email staff on a failure
      • A new page under Tools that lists services that have failed to provision, suspend, unsuspend, cancel, or module renew at least once and information about the service, when it will next be attempted, with an option to clear any delay so the next cron will re-attempt. (Or maybe a new tab under Tools > Logs called "Service Action")
      • A setting for the maximum number of retries before it's no longer attempted.

        Issue Links

          Activity

          Hide
          admin Paul Phillips added a comment -

          Is this so that cron doesn't attempt to activate the same service via a module every 5 minutes indefinitely?

          What kind of backoff, similar to the old auto debit backoff?

          Show
          admin Paul Phillips added a comment - Is this so that cron doesn't attempt to activate the same service via a module every 5 minutes indefinitely? What kind of backoff, similar to the old auto debit backoff?
          Hide
          admin Paul Phillips added a comment - - edited

          After so many attempts, it should stop attempting to provision the service and send an email alert to designated staff. Those staff should be configured for such alerts via the order plugin. My Info > Email Subscription Notices

          Show
          admin Paul Phillips added a comment - - edited After so many attempts, it should stop attempting to provision the service and send an email alert to designated staff. Those staff should be configured for such alerts via the order plugin . My Info > Email Subscription Notices
          Hide
          admin Paul Phillips added a comment -

          Additionally, it may make sense to add a new section under Tools to list impacted services. If a service has failed to provision, suspend, unsuspend, cancel, or module renew then it should be listed in a table with a link to the service or an option to clear the delay so the cron will re-attempt at next run.

          Show
          admin Paul Phillips added a comment - Additionally, it may make sense to add a new section under Tools to list impacted services. If a service has failed to provision, suspend, unsuspend, cancel, or module renew then it should be listed in a table with a link to the service or an option to clear the delay so the cron will re-attempt at next run.
          Hide
          admin Paul Phillips added a comment -

          Replaced by CORE-3274

          Show
          admin Paul Phillips added a comment - Replaced by CORE-3274

            People

            • Assignee:
              Unassigned
              Reporter:
              tyson Tyson Phillips (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: