Uploaded image for project: 'AdMaxLocal'
  1. AdMaxLocal
  2. AML-2199

Deployment status should not be updated once a campaign is terminated

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Not a Bug
    • Affects Version/s: Apponaug
    • Fix Version/s: Wickford
    • Component/s: None
    • Labels:
      None
    • Environment:

      aq-demo2-core1

    • Sprint:
      Wickford - Sprint 7

      Description

      During testing of clearing content assignments, a deployment request was sent that referenced a deleted campaign. This failed because deleted campaigns cannot be "revived". It also resulted in the externalCampaignParentDeployStatus entry for the deleted campaign being updated to 'Failure'. Subsequent requests to getCampaignsByCustomerID() returned this campaign with a 'Failure' deploymentStatus. Any subsequent order deployment that gets sent gets marked with an 'Error' status when AML sees this 'Failure' deploymentStatus.

      After talking with Phej, it seems that we should intercept deployment/status change requests for deleted campaigns in ADS before the deploymentStatus even gets touched (i.e. before even putting the request on the queue). This would provide speedier failures in the ADS requests and never put deleted campaigns into permanent 'Failure' states.

        Attachments

          Activity

            People

            • Assignee:
              jeff.brown Jeff Brown (Inactive)
              Reporter:
              rgardner Ross Gardner
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: