D-44049 - COMMUNITY - Calendar in List View on Laptop Does Not Work to Scroll Mouse Wheel
We have identified an issue where the mouse scroll does not work in the Calendar in List View when in full screen on a 14" laptop monitor. However, the mouse scroll works when the window is moved to a 27" monitor in full screen. It was identified that the problem is related to certain styles in the app.css, and an issue with the function in the ClassBid/WebApp/js/controllers/calendarcontroller.js file. Nonetheless, we resolved this issue through the implementation of a code modification. The styles in app.css are updated, and the function in calendarcontroller.js is corrected to ensure proper mouse scroll functionality. In addition, the issue which also occured in VectorCalendar mode, has been addressed by updating the same function accordingly.
D-44513 - COMMUNITY - Failure of 500 Internal Server Error Displays when Generating Rule Exceptions Report
We resolved an issue where generating the Rule Exceptions Report resulted in a 500 Internal Server Error. This issue occurred due to a timeout during the report generation process. The problem has been fixed by increasing the value of FCGI_TIMEOUT to 1200, which allows the report to complete without error.
Two alternative approaches to this issue are:
- To increase the MYSQL query cache size, though this could potentially introduce additional issues by consuming more memory.
- Improving the efficiency of the underlying database queries could also resolve this, but would require significant effort.
D-45207 - COMMUNITY - No Import Validation When the Pairing Activity Start Date Is Out of the Current Bid Period
We resolved an issue related to the checking of PairingActivity Start and Pairing Start datetimes in relation to period dates. The original issue (D-45207) required converting the datetime to base time zone before comparing it against PeriodDates, but doing so could cause files to fail not correctly when pairings extend beyond the period, with valid PairingLegs starting after the period end. As a result, this requirement is resolved.
Additionally, we identified a potential issue with the existing check of Pairing Start, where files could fail if the overall pairing starts after the period end in UTC, but before the period end in base time. We are testing this scenario to confirm whether the issue exists, and this might require further investigation with test cases.
Nonetheless, to resolve both issues, we have implemented a code modification by reproducing the same logic used in the Pairing start datetime check. Thus, ensuring that the time is converted to base time before comparing it against the period dates.
D-45198 - COMMUNITY - Pairing Name Length Error Implies Only a Length Between 11 and 16 Is Acceptable but Not Checking the 7 Letters for Z
We resolved an issue where the pairing name length error in PBS implies that only lengths between 11 and 16 characters are acceptable but does not check for seven letter "Z" names. This issue is fixed by updating the regex in RaidoConversionHelper.cpp for the second section of the pairing name to prevent matches below seven characters. Additionally, the total length of the pairing name is now checked before continuing. This issue is fixed by updating the regex in RaidoConversionHelper.cpp for the second section of the pairing name to prevent matches below seven characters. Additionally, the total length of the pairing name is now checked before continuing.
D-45058 - COMMUNITY - Wrong Result When Analyzing PreferOff on Several Dates
An issue when several dates are chosen for PreferOff, some pairings are removed from the analyzer when they match the bidline, while others are shown with all their pairingOnDates matching the bidline, has been resolved. This issue is fixed by modifying the code to ensure consistent handling of pairings that match the bidline and to correct the circle color update process in the analyzer (from being not valid).
Below is the list of Pairings for ACA with Bidder 066009 for August 2024:
After reviewing the previous list, pairing T5001 matches the bidline PreferOff on the 25th and 26th, but it does not appear in the analyzer.
Meanwhile, pairing T5011 (shown on the next slide) shows all its pairings on dates that match the bidline PreferOff for the 25th and 26th, while T5008 does not show the 26th as matching the bidline.
D-42387 - COMMUNITY - Ability to Add Preferences to Award Reserve
We resolved an issue where, when several dates are chosen for PreferOff, some pairings are removed from the analyzer when they match the bidline, while others are shown with all their pairingOnDates matching the bidline. In addition, another issue is that the update of the circle colors in the analyzer is not valid. These issues have been fixed by modifying the code to ensure consistent handling of pairings that match the bidline, and correcting the circle color update process in the analyzer.
D-45063 - COMMUNITY - Admin UI - ASA/ASAP- '500 Internal Server Error' Appears which Causes the System Login to Be Disabled When Adding a Crew Position Under
Incorrect Crew Type
An issue where a '500 Internal Server Error' occurs when adding a crew position under the default Pilot crew type has been identified, and addressed. This happens when the default Pilot crew type, which is not the correct crew type, is selected, causing the system login to be disabled. Nonetheless, a code modification is now implemented to resolve the webapp crash and prevent further disruptions. Additionally, we decided to align the crew type(s) UI with customer-specific crew types.
1. ASA on RH8:
2. ASAP on RH8:
A similar issue occurs for ASAP, where a '500 Internal Server Error' also appears when the user attempts to add a new crew position under the Cabin crew type.
3. ASAP on RH6:
4. ASA on RH6- wrong crew type is saved:
D-44816 - COMMUNITY - Webapp - Pairings Filter Issue in Certain Scenarios
We resolved an issue where the Webapp-Pairings Filter did not work properly in some scenarios. This issue has been fixed by adding a code modification to locally convert the pairing credit time to a float. This ensures that the filter properly compares the credit values, as the filter value is already converted to a float.
There are three scenarios:
- Scenario One: On the Pairings tab, searching for the criteria 'Pairing In Period Credit = 2.08' (ATL-765-A) returned zero pairings.
- Scenario Two: On the Pairings tab, searching for the criteria 'Pairing Carry-out Credit = 10.00' (ATL-765-A) returned zero pairings.
- Scenario Three: On the Pairings tab, searching for the criteria 'Pairing Total Credit = 7.59' (ATL-73N-A) returned zero pairings.
Scenario 1: On the Pairings tab, searching for the criteria 'Pairing In Period Credit = 2.08' (ATL-765-A) returned zero pairings.
Scenario One continued.
Scenario Two: On the Pairings tab, searching for the criteria 'Pairing Carry-out Credit = 10.00' (ATL-765-A) returned zero pairings.
Scenario Two continued.
Scenario Three: On the Pairings tab, searching for the criteria 'Pairing Total Credit = 7.59' (ATL-73N-A) returned zero pairings.
Scenario Three continued.
D-45649 - COMMUNITY - Calendar Display Issues With and Without Scrolling
We corrected an issue where there were problems with the display of the calendar with, and without scrolling in SCX when activities are assigned to the bidder. Nonetheless, we have resolved the issue where events were not displayed correctly in the last row of the calendar. Additionally, when the window height was too low, scrolling issues, and visibility problems occurred at the end of the calendar. This issue occurs because the activities have four lines of details: the name of the activity, Start, End, and Total Credit. Due to the amount of lines, display problems arose, causing issues with viewing the calendar properly. This issue is now resolved.
Examples of issues that occur when viewing the calendar:
1. Aditional space between calendar rows (without scrolling)
2. When the activity is placed in the last row of the calendar, it extends beyond the width of the row.
3. The entire last row of the calendar is not visible when scrolling.
D-43516 - ACA - Pairing Number with Condition>Range in Pairing Search
We identified an issue where, when using the Pairing search function in the Pairings tab, and selecting the parameter “Pairing Number > Condition > Range,” entering values for the range, and clicking Apply returns pairings in the search. However, if you attempt to add any additional parameters to the seach by clicking on “Back To Pairing Number” in the Condition menu, no checkmark appears beside the previously selected Condition option. Similarly, if you click “Back To Pairing Preferences” from the Pairing Number menu, there is also no checkmark beside the Pairing Number preference. When a new preference is chosen, clicking Apply only considers the newly selected preference(s), and does not include the previously selected “Pairing Number > Condition > Range”. This issue occurs only when the Range option is used where the root cause is a bug that causes the previously selected filters to reset. Nonetheless, we resolved this issue by implementing a code modification. This change ensures the system references the correct field in the object, allowing it to recognize whether the filter is still configured. Thus, preventing the resetting of filter values, and ensuring that previously chosen parameters are retained when applying new preferences.
D-45828 - ACA - Possibility to Copy Certain Prefer Off Bid Lines to Award Reserve Bid Group
We corrected an issue where certain types of Prefer Off bid lines could be copied to the Award Reserve Bid Group, which should be prohibited. This issue occurred due to a bug in the process, despite existing tests designed to prevent the paste action in an Award Reserve Bid Group from being executed. Nevetheless, we resolved this issue by modifying the code in bidlinevalidateservice.js. Specifically, we added a '?' after preferOffConfig in the first IF statement within the ValidatePreferOff...() functions. This fix ensures that an error message is returned, and the paste button is not active when the selected bid group is an Award Reserve.
- Dates Range
- Days Of Week List
- Days Of Week Range
- Weekends All or Nothing
- Weekends Else Start Next Bid Group.
D-44157 - ASA - Wrong Pairing Preferences Filtering for "Average Daily TFP"
An issue where the "Average Daily TFP" does not display correctly in the Pairings Tab, and also affects the Analyzer function on the Bids tab has been identified. This occurs due to the way the average daily TFP is computed. Nevertheless, we have resolved this issue by reviewing and updating the code that computes the average daily TFP. The issue is now fixed, and the correct value is displayed in both the Pairings Tab, and the Analyzer function on the Bids tab.
Present when sorting by Pairing Number
Present when Sorting by Average Daily TFP
Present when Sorting by Average Daily TFP - Continued
Present when Sorting by Average Daily TFP - Continued
Present when Sorting by Average Daily TFP - Continued
Present when Sorting by Average Daily TFP - Continued
Present when Sorting by Average Daily TFP - Continued.
D-44172 - ASA - Sort By Average TFP - Broken
An issue where the Sort By Avg Daily TFP feature produces scattered discrepancies has been identified. This occurs due to the averageDailyCredit being stored as a string in pairingdata.js, which results in ordering that is not correct when sorting by dailyAverageCredit. Specifically, "10" is placed before "2" due to the string comparison. It has been identified that the 6.1 credit value is the major problem in this case. This is resolved by modifying the code to convert the string to a float using parseFloat. The updated code is as follows: this.averageDailyCredit = parseFloat(getCreditInFormat((parseDecimalInt(strCredit) / parseDecimalInt(strLength)), strPeriodName));
Nonetheless, this change ensures that the averageDailyCredit is correctly calculated, and ordered.
D-45907 - ASA - Aos Pairing Import Fails on RHEL8
We have discovered an issue where a file provided by the customer hangs when attempting to import it on RHEL8. This issue does not occur on RHEL6, where the same file imports successfully with no incident. We resolved this issue by investigating the differences in the import process between RHEL6 and RHEL8. A code modification has been made to address the specific compatibility issue on RHEL8, ensuring the import process completes successfully without hanging.
D-44969 - ASAP- The FO Run Crashes with Error 'PBS for run exceeded maximum age'
An issue where the FO run fails with the error 'PBS for run exceeded maximum age' during the ASAP- ANC-737-FO process is resolved. This occurs when attempting to perform the FO run, causing the process to crash (see images below).
Nonetheless, the crash is caused by the initialization of two boost::optional variables to boost::optional(NULL) not correctly being done. These variables are not properly initialized to null, resulting in non-null values after initialization. This leads to null activities being inserted into SubCands, which are later assumed to be non-null, causing the crash.The faulty initialization to boost::optional(NULL) was introduced during the RH8 work to prevent build warnings. Reverting to the old code that initializes to boost::optional() resolves the crash in a DEBUG build but reintroduces build warnings in OPT builds. These warnings are related to the two optional variables being "may be used uninitialized," which are found to be invalid warnings.The final resolution involves replacing the boost::optional with std::optional and initializing them to std::optional(). This fix resolves the crash, and eliminates the build warnings, thus improving both stability, and build performance.
D-45305 - ASA & DAL - Enable Pairing Filtered Award - Layover - Of Duration does Not Work with option (> < =)
An issue where the Enable Pairing Filtered Award - Layover - Of Duration did not work with the options (>, <, =) is resolved.
D-45832 - ASAP/DAL - WebApp Calendar Tab Displays Only Five Rows
We resolved an issue where the WebApp Calendar tab displays only five rows. This occurs because the indexes of the loops responsible for generating the calendar lines are not defined correctly. This issue is fixed through a code modification that properly defines the indexes.
For ASAP Bidders see only five rows (weeks) in the WebApp Calendar tab, preventing them from viewing June 1st (Sat) in the June month. This issue is fixed by updating the calendar view logic to ensure all weeks in the month display correctly, including the first day of June. As a result, June 1st is now visible when selecting the June month, not just the May month.
D-45832 - ASAP/DAL - WebApp Calendar Tab Displays Only Five Rows - Continued
For DAL, we have resolved an issue where January 31st is not showing on the February calendar. This issue is fixed by updating the calendar view logic to correctly display the last day of January, ensuring it appears on the February calendar. As a result, January 31 is now visible when viewing the February month.
D-41409 - DAL - Analyzer Showing Not Correct Information for Carryout Pairings
An issue where the Analyzer marks every departure of a pairing as filtered out by the “Avoid Pairings If Carryout > 0 Days” rule has been identified. This occurs when a pilot has a line with the “Avoid Pairings If Carryout > 0 Days” rule, and a subsequent Award includes a trip that operates throughout the entire month, with some departures being carryout and others not. In this case, the Analyzer marks all departures of the pairing as filtered out, even though only a few should be.
This is resolved by updating the logic in the Analyzer to correctly handle situations where only certain departures of the pairing should be filtered out, ensuring the correct departures are marked as filtered.
D-42703 - DAL - Applying Filter on Training Screen Hangs Loading (RHEL8)
We resolved an issue where selecting a filter, such as Event Period or Event Location, on the Training Screen, and clicking "Apply" causes the screen to freeze (displays the spinning wheel and "Loading"). This issue is fixed by updating the filter handling logic to ensure the correct processing of the selected filters. Additionally, the system now properly processes the filter selections, and completes the loading without hanging.
Example: Occurs when applying ANY TYPE of Training Preference. Note: We were able to reproduce the issue in PROD 23.6-18.
D-44174 - DAL - Duty On Dates Filter Does Not Fully Show Results for IF Condition
We resolved an issue where the DutyOn dates filter does not completely show the results for the IF condition, particularly when filtering for "If" vs "If not." This issue, present in Trunk, does not filter correctly, and causes pairings starting on the 11th to be incorrectly included in the total number of pairings. This is fixed by a modification in code to update the filtering logic to ensure accurate results for both "IF", and "IF NOT" conditions. As a result, the DutyOn dates filter now functions as expected, properly excluding, or including pairings based on the condition.
Example: 1521/1804 for IF Not - BUT IT SHOULD BE 1436, based on the IF below.This should be excluded, as it starts on a date we specifically asked it NOT to include.
Example: If it is showing 368/1804 for IF
D-45062 - DAL- Webapp - The Newly Added Employee Number is Not Shown in Award/Avoid Employee Bid Option
We have discovered an issue where the newly added employee number from category A is not shown in the Award/Avoid employee bid option for the category B employee. This issue is now resolved.
D-45847 - DAL - Applying Filter on Training Screen Hangs During Loading in Specific Case
An issue when trying to filter Training with a complex filter, the training search hangs, unless Event Location, Simulator Type, Event Touches (with Days Of Week List), and Identifier are used, has been resolved. This issue occurs because some actions in certain objects are undefined, causing the filtering process to fail. We have resolved this issue by implementing a code modification to properly define, and handle the actions within these objects. This fix ensures that the training search functions correctly without hanging when using complex filters.
D-45415 - ENY - Incorrect Number of GDO Available for the Bidder
An issue where the ENY Bidder is able to take three days of GDO in the actual period, despite six days of GDO being available in the row, has been identified, and addressed. This occurs when the ENY Bidder has vacation at the end of the previous period. Additionally, when four GDO days are selected in the row, a wrong error message displays, stating there are gaps in the selected days, which is not true. Nonetheless, a code modification has been implemented to remove the hardcoded '3', and instead use the value from the configuration for the allowed number of GDOs. Additionally, the function that checks for gaps between the selected days, and the vacation block has been fixed.
D-45897 - FLE - Import of N-OC Pairings file Not Possible due to Invalid Validation of Start Element
For FLE, we resolved an issue with importing the N-OC Pairings file when the file contains Pairings with a Start date before the period begins. This issue has been fixed by adding a code modification to validate the Start Element only for TOPS Pairing files, ensuring that files for N-OC are handled correctly without restrictions on the Start Date.
Example: In the attached file there are pairings which start in June 2024, but the pairing file is for July 2024.
For N-OC, importing this type of file should be possible.
D-44617 - JBU - Problems with Synchronizing Bid Periods
For JBU, we identified an issue where some bidders cannot view bids from September 2024 when attempting to synchronize bid periods. After log in, the system automatically syncs the two months without displaying any errors. However, when users access the bidding interface, and try to sync the September 2024 bid period, an error occurs.
Bidders with this issue:
- 25110
- 67022
- 35231
- 54758.
Bidder 25370 (Rops), has no issue, because there are no pairings assigned for September, thus the September period can be synchronized in the WebApp.
Resolution Details:
JBU modifications to the CA category removed all the CA pairings as the period data table shows no pairings. This issue results from a synchronization problem, where the system fails to properly retrieve, and display the September 2024 bid data during the sync process. We resolved this issue by implementing a fix that ensures the bid periods are correctly synchronizes, and displays in the bidding interface.
D-44942 - JBU - Import of CrewPlan Pairing File Fails if '&' is Inside the File
We have discovered an issue where the import of the CrewPlan Pairing file fails if there is an '&' symbol inside the file. The import fails on JBU UAT but works on JBU PROD. This issue arises because PROD is using RHEL6, whilst UAT is using RHEL8. The '&' sign in the imported file causes the frontend Perl code to replace it with &amlp;. As a result, the following bytes in the file are shifted by four characters, causing the data to be misaligned. This misalignment prevents users from parsing the file, as we expect data at specific offsets, however it has been shifted by four bytes. The root cause is based on the behavior of XML::Bare::xmlin, which uses an external Perl library that behaves differently on RHEL8 than on RHEL6. We have resolved this issue by switching to the XMLin function, which allows consistent behavior on both systems, ensuring the file is processed correctly.
D-45286 - JBU - Webapp SSO Login Page Cycling Issue
A cycling behavior has been identified by one of the JBU users on the RH8 UAT PBS. When the user logs into the WebApp using SSO, the login is not effective, and the browser cycles indefinitely between the WebApp page, and the SSO login page. This behavior can only be stopped by clicking the back button (or another key, not clearly identified). While intermittent, this issue occurred enough times to be considered a serious problem that needed resolution.
This issue:
- Happened less than 25% of the time on iPads using Chrome or Safari, with Chrome being the most affected.
- Rarely occurred on Mac (less than 5% of the time) and was seen only on Safari.
- After 2-Factor Authentication, the system continuously redirects between the WebApp address and the MS login address.
We resolved this issue by adapting the modification in app.js to update authservice.js. The fix involves introducing a 200ms delay before retrieving the token, ensuring the login process works correctly without causing an endless redirect loop.
D-45318 - JBU - TOPS Error Message Makes Reference to Another Feature (RAIDO)
We corrected an issue where the error message stated, "TOPS" instead of "RAIDO". This issue occurred when reusing code, where some error messages were not updated, resulting in the message incorrectly referencing "TOPS" instead of "RAIDO." A code modification has been implemented to ensure that the error message now correctly states "RAIDO".
Example:
D-45355 - JBU - Converting TOPS Crew - RosterActivity - No Error Message for Some Days, Whose Absence Ends After the Period End
We resolved an issue where converting TOPS CREW to RosterActivity in PBS did not display an error message for some days where the absence ended after the period end. This issue is resolved.
D-45362 - JBU - TOPS Error Message Makes Reference to Another Feature (N-OC)
An issue where the TOPS Error message makes reference to another feature (N-OC) has been identified. This occurs when reusing code, where some error messages were not updated, causing the error message to state "TOPS" instead of "N-OC." This has been resolved and the correct error message now displays.
Example:
D-45718 - JZA - Not Able to Resubmit Bid After Adding Additional Bids
We corrected an issue where it is not possible to resubmit a bid under specific conditions. The issue occurs under specific conditions:
- A vacationGDO bidline with one day is selected
- The bid is submitted
- The synchronize button is pressed.
Once the above is set, the bidline is stored in XML format and then restored back to JSON. The JSON->XML->JSON translation is not symmetrical, causing an array with a single Date object to be reduced to just a single Date object. Nonetheless, we resolved this by ensuring the system can accept either an array with multiple Date objects, or a single Date object, maintaining the integrity of the bidline during the process.
D-45995 - JZA - RH8/RH6 - Vacation GDO can not be Added after Vacation Block and GDO Day as Vacation Extension Added via Admin UI
We corrected an issue where Vacation GDO could not be added after a Vacation block, and a GDO day when a Vacation Extension was added via the Admin UI. The system was preventing the addition of the Vacation GDO under these specific conditions, even though it should have been possible. This issue is resolved by updating the way of checking the validity of GDO to allow the addition of Vacation GDO after a Vacation block, and a GDO day when a Vacation Extension is in place, ensuring smooth functionality.
Scenario1: Five days vacation on July 10-14th and one GDO on July 15th from current period.
Scenario 2: Five days vacation on July 10-14th and one GDO on July 09th from current period.
D-44899 - SIL - Error Instead of Warning When Loading N-OC Crew File
An issue where SIL is showing an error message instead of a warning during crew loading has been resolved. Previously, the system would display a warning that could be bypassed, allowing the crew load to continue. Recently, however, this behavior changed, and an error message now appears, preventing the loading of crew members. Nevertheless, this issue has been resolved by adding return messages, and validation during the TOPS Crew import. To meet the validation requirements for TOPS, additional tests were implemented, which display errors when certain elements in the file are not correct. Furthermore, a code modification was made for N-OC to store the previous state, ensuring that the correct validation process is followed, whilst maintaining the desired behavior.
D-45101 - SCX - Training Bids - Bidder Is Not Able to Add 'WaiveTraining Credit' Bid When There Is 'Set Condition Training GDO' Bid Exists
The bidder is not able to add 'WaiveTraining Credit' bid when there is 'Set Condition Training GDO' bid exists:
Note: Delete 'Set Condition Training GDO' bid, then 'WaiveTraining Credit' bid can be added.
D-46157 - SCX - FastCGI FalconConversionUI_SCX Process Terminates During AIMS Import
An issue where the FastCGI FalconConversionUI_SCX process terminates during AIMS Import has been resolved. The issue occurs during the importing of AIMS Absences & History file over the December period, causing the import to fail, and produce a 500 Internal Server Error dialog. This error happens when the web server cannot communicate with the FCGI process (/var/www/fcgi-bin/FalconConversionUI_SCX) as the process is terminated due to a segmentation fault. We resolved this issue by manually restarting the environment web server.
D-45925 - UCA - Award Split Duty Trip
We have discovered an issue where pairings with 'split duty' should have <LegalException>ZS</LegalException> inside a pairingActivity, however, they did not. While this is properly read during import and stored in the database, Bidders who try to filter for pairings with the ‘split duty’ flag in the Pairings tab are shown all pairings (for example, the filter returns 58 out of 58), instead of only those that have 'split duty'. This issue has been resolved by adding specific handling for the Any/Every condition in the case of the StandUp (split duty) filter, as the current logic for filtering did not properly account for these cases.
Bidders can select "ANY" or "EVERY" for the filter:
- "ANY" - means that a pairing is matched by the filter if any of the duties is a split duty
- "EVERY" - means the pairing is matched only if all duties are split duty.
D-46258 - UCA - RH8 Server Import Error - COMMUNTIY ALL NOC RH8 Customers
We corrected an issue where the error message stated, "Unable to download data due to internal server error" or "Unable to connect to Server due to security certificate" when trying to import data from NOC into PBS in a new RHEL8 environment. This issue occurred because of unclear logic in the code, where the system used a generic message without specifying the exact error code. As a result, it was unclear whether the issue was related to a certificate or something else. Nonetheless, this issue has been resolved by fixing the usage of a temporary variable. A named string is now used, thus ensuring that the variable does not go out of scope. Additionally, we removed a few const_cast instances in the same file, allowing for more precise error handling and clearer messaging when importing data.
Note: Airlines that have the integrated NOC imports: ASH, BWA, CJT, FLE, JSX, MXY, NLBS, NVB, NVBC, NVEQ, NVML, NVRS, POE, SIL, UCA, VXP, WGN
One issue to be fixed in PbsSslRequestHandler.cpp is related to the use of the temporary object "oss.str()". The pointer pHostPort currently points to deleted memory, which may have worked with the older GCC version used for RHEL6. However, on RHEL8, printing pHostPort results in invalid values. Once this is fixed, the connection is properly established.
D-46259 - VXP - Historical Pairing Error - COMMUNITY FOR NOC & PBS users
An issue with data in the Historical Pairings file, where historical pairings are not described using the correct dates of the related historical period, has been resolved. For example, using "FromDate: 2024-12-02 ToDate: 2025-01-03" for historical pairings from December 2024 generates an error message during import, as the end date falls within the active period. The correct value should be "FromDate: 2024-12-01 ToDate: 2025-12-31," which aligns with the start, and end dates of the historical period. Nonetheless, we resolved this issue by implementing a validation in the import process to ensure that the pairing dates correctly match the historical period. This fix prevents the error, and ensures that Historical Pairing files are imported correctly.