Details

    • Type: Customer Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: CFA 2022R3
    • Fix Version/s: CFA 2022R5
    • Component/s: Imports
    • Labels:
      None
    • VTask #:
      VTASK0495916
    • Root cause - Reason:
      Code defect
    • Root Cause:
      Code changes are made

      Description

      CFA is continuing to receive calls about low forecasted usage when placing truck orders.
       

      They have spot checked a few restaurants and they are all missing Sales Item Forecasts for multiple items.
       

      Usually we handle those requests by re-importing the missing forecast days.

      The following are 2 errors where we found the task didn't continue to import the forecast after the error occurs, can we look for an improvements to get a retry to re-import the missing files after getting the error or just skip the file that caused the error and proceed with the other files.

      For day 7/25 -we should have imported on 7//10 found error message below and this is why we didn't import 7/25 .
      Error getting or saving forecast data for 00001 from https://api.cfascforecastprod.cfahome.com/v1/forecast/status/00001/?fromDate=07-25-2022&toDate=07-30-2022 to W:\MacromatiX\SiteData\Chick-fil-a\DataImports\ForecastAWS\Forecast_{storenumber}_{forecastdate}.xml: The remote name could not be resolved: 'api.cfascforecastprod.cfahome.com'
      
      Following error caused Forecast job to stop and is the reason why all stores didn't get forecast for 8/1. 
      Error getting or saving forecast data for 00016 from https://api.cfascforecastprod.cfahome.com/v1/forecast/status/00016/?fromDate=08-01-2022&toDate=08-06-2022 to W:\MacromatiX\SiteData\Chick-fil-a\DataImports\ForecastAWS\Forecast_{storenumber}_{forecastdate}.xml: could not execute query  [ SELECT this_.ForecastId as ForecastId149_0_, this_.EntityId as EntityId149_0_, this_.BusinessDay as Business3_149_0_, this_.GenerationDate as Generati4_149_0_, this_.ExternalGenerationDate as External5_149_0_, this_.Status as Status149_0_, this_.SystemSales as SystemSa7_149_0_, this_.SystemTransactionCount as SystemTr8_149_0_, this_.ManagerSales as ManagerS9_149_0_, this_.ManagerTransactionCount as Manager10_149_0_, this_.ItemMgrDetailsChanged as ItemMgr11_149_0_, this_.ForecastBasis as Forecas12_149_0_ FROM Forecasting.Forecast this_ WHERE this_.EntityId = @p0 and this_.BusinessDay between @p1 and @p2 ]  Positional parameters:  #0>17 #1>8/1/2022 12:00:00 AM #2>8/7/2022 12:00:00 AM  [SQL: SELECT this_.ForecastId as ForecastId149_0_, this_.EntityId as EntityId149_0_, this_.BusinessDay as Business3_149_0_, this_.GenerationDate as Generati4_149_0_, this_.ExternalGenerationDate as External5_149_0_, this_.Status as Status149_0_, this_.SystemSales as SystemSa7_149_0_, this_.SystemTransactionCount as SystemTr8_149_0_, this_.ManagerSales as ManagerS9_149_0_, this_.ManagerTransactionCount as Manager10_149_0_, this_.ItemMgrDetailsChanged as ItemMgr11_149_0_, this_.ForecastBasis as Forecas12_149_0_ FROM Forecasting.Forecast this_ WHERE this_.EntityId = @p0 and this_.BusinessDay between @p1 and @p2]
      

        Attachments

        1. CFAMX-21340 CFA Forecasting import errors.png
          CFAMX-21340 CFA Forecasting import errors.png
          138 kB
        2. image-2022-08-24-17-53-46-178.png
          image-2022-08-24-17-53-46-178.png
          138 kB
        3. SBX_AWS.postman_collection.json
          4 kB
        4. screenshot-1.png
          screenshot-1.png
          875 kB
        5. screenshot-2.png
          screenshot-2.png
          214 kB
        6. screenshot-3.png
          screenshot-3.png
          30 kB

          Issue Links

            Activity

              People

              • Assignee:
                stacy.privalova Stacy Privalova
                Reporter:
                wesam.el-gendy Wesam El-Gendy
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.