Approach: Create FDD for each slot.
Create FDDs: We will create an FDD for each slot with the scheduled_start_time set to the start time of the slot. For example, if we have 10,000 records in a file and 3 slots, we will create 10,000 FDDs for each slot, resulting in a total of 30,000 FDD for a single file. These FDD will be queued for execution according to the slot start time. Additionally, we will add a new variable to the FDDs to denote the slot.
We will create FDD for uploading day slots only at the time of upload.Other day slot FDD will be created by scheduler at 00 hour as per slot defined.
If no slot is selected at the time of uploading the file then FDD will create without slot and work the same as current flow.
Slot Functionality will be working only for those campaigns uploaded from our system.
Maximum slots in a day is 2 and the campaign will be scheduled only for 30 days.
Slot time must be under working time (Flow working time).
If the csv file contains the schedule time field and campaign created in slot then schedule time will be slot start time that means ignore schedule time fields.
NOTE : All file upload process and scheduler for slot will be processed on KFP.
Execution: During execution on KP, we will perform all essential checks as currently practiced, including verifying the slot time. If the execution time falls outside the designated slot time, the task will be marked as a failure (out of slot time). We will not reschedule the task, even if reattempts and rescheduling within the next business hours are defined in the flow.
Reports: There will be no changes required in the approach for EOD and raw reports. Currently, EOD reports are generated based on the FlowExecutionAttemptDetailDocument start time. Raw reports are generated based on start time, phonon_uuid, request_id, and other relevant numbers.
Report Count For campaign Manager
On page load data will be the current date.
Uploaded Record : Total record in file.
Attempted Records : Total FDD other then IN PROGRESS status.Attempted Records will be more then total record if multiple slots.
Negative Upload Records : All Negative Records uploaded for campaign.
Pending Records : All FDD count IN PROGRESS status.
Upload Negative Number : Uploading negative number file process.
1.We will store a negative number in Mysql corresponding to request_id.
2. At the time of uploading a file any slot is defined for uploading day then we will update FDD as Negative 3.Number and check in KP.
4.When the scheduler will create FDD of scheduled slot at the time will check negative number repository for corresponding requst_id and will not create FDD.
Need to maintain negative file upload for reporting.
SOP (Standard Operating Procedure):
Define the number of slots in a single day.
Establish a minimum slot gap between the file upload and upload of slot details / blacklist number details etc.
If the number of records processed within a given slot is below the system's capacity, the slot will be marked as FAILED. Therefore, the number of records in each slot should align with the system’s capacity
0 Comments