Last Updated February 1, 2024 at 1:09 PM ET
The FY2023 LSA Submission period is now closed
The LSA Module of HDX 2.0 has now closed for the FY23 period.
As usual, throughout the submission period, we will use this space to provide general information about current HDX 2.0 system issues. Please check back regularly to remain up-to-date on the status of all bugs and flag issues we are actively addressing.
As usual, throughout the submission period, we will use this space to provide general information about current HDX 2.0 system issues. Please check back regularly to remain up-to-date on the status of all bugs and flag issues we are actively addressing.
Current Outstanding Error/Warning/Interface Issues
Newest on top
- Flags 1127, 1131, and 1135: This flag is comparing the count of people who selected a single race category (i.e. not Hispanic/Latina/e/o) in the LSA to the count of people in the PIT Count who selected that race category, regardless of the ethnicity they chose. As a result, there will always be a notable difference in CoCs with large Hispanic/Latina/e/o populations. CoCs can simply note the presence of a large population that would cause this apparent discrepancy in their notes and the warning will be considered resolved. This flag will be corrected in future LSA cycles. (posted 1/10)
- Flags 1003-1050, 1059, 1060, 1069, and 1070: The utilization rate in these flags is slightly off for projects that were not operating or HMIS-participating for the full report period. In general, the differences are minor and correcting the calculation would still result in receiving the flag. If you receive a flag like this, please explain the low or high utilization in general terms. If you feel that an adjusted calculation would result in a typical utilization rate, you may note that in the comment. (posted 1/10)
- Red Banner errors: CoCs may receive a red banner across the top of their Flag Report tab that reads, "There is an issue with the data quality checks on your dataset. Please report this issue to your data liaison as soon as possible." These are issues caused by unknown structural issues with your upload file and must be handled individually. Once you inform your data liaison, we will investigate the cause of the issue and let you know. (posted 11/14)
Resolved Error/Warning Issues
Newest on top
- Flags 813-817: Several geocodes for AIAN Tribal Areas were missing. The geocode list has been updated to include the complete list. Any users who uploaded prior to the resolution date/time may now reupload to clear any inaccurate instances of the flags. (resolved 1/9 6:30 PM ET)
- Flags 901-905, 983-1007, 1009-1013, 1015-1019, 1021-1025, 1027-1031, 1033-1037, 1039-1043, and 1045-1049: These flags were not tripping at all this year. Any users who uploaded prior to the resolution date/time may now reupload to determine if they receive these flags. (resolved 12/21 7:30 PM)
- Flags 1341-1343: New flags have been added to address the project-type restrictions for three new funding sources added to the FY24 data standards. Any users who uploaded prior to the resolution date/time may now reupload to determine if they receive these flags. (resolved 12/21 7:30 PM)
- Flag 1140: This flag was inaccurately including DV-beds. It has been corrected to exclude those. Any users who uploaded prior to the resolution date/time may now reupload to clear any inaccurate instances of the flag. (resolved 12/21 7:30 PM ET)
- Flags 1008 and 1032-1050: The percentage in the flag text has been updated to display correctly. There is no need to reupload, as this fix only affects the text of your flags. (posted 12/13; resolved 12/21 7:30 PM)
- Flag 461: There was an issue in the underlying LSA calculation that feeds this flag. We have updated the sample code and related documentation and have requested that vendors update their code to reflect the correction. If you received this flag, you will need to re-run and re-upload your report when your vendor notifies you that the update has been made. (posted 12/8; resolved 12/21 7:30 PM)
- Flag 1338: There was an error in the underlying LSA calculation that feeds this flag. We have updated the sample code and related documentation and have requested that vendors update their code to reflect the correction. If you received this flag, you will need to re-run and re-upload your report when your vendor notifies you that the update has been made. (posted 11/30; resolved 7:30 PM)
Note that CoCs may still get this flag even after an update by their vendor. Any remaining instances will reflect real data quality issues. As of 12/21 at 7:30 PM ET, this flag was converted to a warning. - Stella P: Stellavization has been reactivated for the FY23 upload period. (resolved 12/11 9:00 AM ET)
- Red Banner Bug: On 12/6 and 12/7, not all flags were displaying, as indicated by an increase in red banner errors. All CoCs who received red banners on those dates should now reupload to allow the file to complete processing, clear the red banner, and display all flags. If you receive a red banner after reuploading, please reach out to your Review Team in accordance with the normal process for handling red banners listed above. (posted 12/7; resolved 12/7 6:27 PM ET)
- Flag 1315: This flag was tripping when a project's operating end date was equal to the lookback start date. This is permissible, so the flag has been updated to trip only if the operating end date is earlier than the lookback start date. Any users who uploaded prior to the resolution date/time may now reupload to clear any inaccurate instances of the flags (posted 11/30; resolved 12/7 6:27 PM ET)
- Flags 813-817: Some CoCs may have encountered flags related to inaccurate geocodes. The geocode list has been updated. Any users who uploaded prior to the resolution date/time may now reupload to clear any inaccurate instances of the flags (resolved 12/7 6:27 PM ET)
- Flag 792: This flag indicates that project types other than PSH are storing data about dedicated CH beds. We are able to disregard this extraneous data, so the flag has been removed. Any users who uploaded prior to the resolution date/time may now reupload to clear any inaccurate instances of the flags. (resolved 12/7 6:27 PM ET)
- Flag 1301: One iteration of upload error 1301 was inaccurately comparing Populations 52 (parenting child) and 35 (white and Hispanic/Latina/e/o). It has been corrected to compare 52 (parenting child) and 46 (parenting child households), Any users who were unable to successfully upload due to this error will now be able to do so. (resolved 12/7 6:27 PM ET)
- Missing Flags on 12/6 uploads: It has come to our attention that a certain subset of flags (those that apply to "official" uploads but not to local upload files, or roughly 20% of the 1,000 flags that display in interface) were not calculating between 12/5 at 5:30 PM ET and 12/6 at 10:30 PM ET. This issue has been resolved. All CoCs who uploaded an Official HUD Review file between those times will need to reupload. (posted 12/7 11:22 AM ET and resolved 12/6 at 10:30 PM)
- Flags 1139-1197: The resurgence of issues with the following flags has been resolved: 1139, 1140, 1143, 1144, 1147-1154, 1157-1160, 1163, 1164, 1167-1169, 1171, 1176, 1178, 1183, 1185-1187, 1191, 1192, 1196, 1197. Implementations that use non-numeric values in their Project IDs who upload now will find accurate values populating for the LSA-calculation of available beds on the night of the HIC. At this time, users with non-numeric Project IDs who uploaded prior to the resolution date/time should reupload to clear any inaccurate instances of this flag. (posted 12/6; resolved 12/6 at 10:30 PM)
- Flag statuses reverting to "Note Required": Some CoC users were seeing their flag statuses revert to the default status of “Note Required”. Uploads going forward should no longer have this issue. Note that all warning flags start with a default status of Note Required. If you have not entered notes, that is the correct status. No notes were lost at any point and, regardless of status, your review team has always been able to see and review your notes. Going forward, when the flag status is updated it will remain in the correct updated status and not revert back to Note Required. (posted 11/30; resolved 12/5 5:30 PM ET)
- Flag visibility: Some CoC Users were temporarily unable to see flags on their uploads. The issue has been resolved and all CoC users with read access or higher should be able to see their flags again (posted 11/29; resolved 11/29 5:30 PM ET)
- Flags 1139-1198: The following warning flags in this range were calculating the count of beds to compare to the HIC submission inaccurately: 1139, 1140, 1143, 1144, 1147-1154, 1157-1160, 1163, 1164, 1167-1169, 1171, 1176, 1178, 1183, 1185-1187, 1191, 1192, 1196, 1197. The calculation of bed counts on the HIC date has been fixed to accurately reflect available beds so that these flags are now correct. Any users who uploaded prior to the resolution date/time will need to reupload to clear any inaccurate instances of the flags (posted 11/15; resolved 11/27 6:12 PM ET). Note that the following flags, which are also in that range, appear to have been accurate and have not been adjusted: 1141, 1142, 1145, 1146, 1155, 1156, 1161, 1162, 1165, 1166, 1172, 1174, 1179, 1181, 1188-1190, 1193-1195, 1198.
- Flag 461: This flag was tripping inaccurately for acceptable combinations of values. The list of acceptable combinations was fixed. Any users who uploaded prior to the resolution date/time will need to reupload to clear any inaccurate instances of this flag (posted 11/14; resolved 11/16 5:50 PM ET).
- Flag 684-900s: Some of the 684-900s series of flags were tripping for the incorrect population. The Native Hawaiian or Pacific Islander, Hispanic/Latina/e/o veteran population group was being compared to the overall Hispanic/Latina/e/o veteran population. The relationship was fixed. Any users who uploaded prior to the resolution date/time will need to reupload to clear any inaccurate instances of this flag (posted 11/14; resolved 11/16 5:50 PM ET).
- Flag 687: This flag was tripping in situations that are possible. The LSACalculated number can be larger than the the LSAHousehold project-specific field (e.g. ESTFleeingDV) in some situations. The calculation was corrected it so it is compared to HHFleeingDV instead, which cannot be smaller than the LSACalculated value. Any users who uploaded prior to the resolution date/time will need to reupload to clear any inaccurate instances of this flag (posted 11/16; resolved 11/16 5:50 PM ET).
- Flag 781: This flag was tripping for RRH-SO projects, which would not be expected to have Inventory records, but might have Data Quality rows for the project ID in the LSACalculated file. The flag was fixed so it will not trigger if the project has only Data Quality rows (ReportRows greater than 900) in the LSACalculated file. Any users who uploaded prior to the resolution date/time will need to reupload to clear any inaccurate instances of this flag (posted 11/14; resolved 11/16 5:50 PM ET).