#4543 FAC - Bug: Missing DCF?

[RanyeM]

Describe the bug

Bug shared via helpdesk at https://fac-gov.zendesk.com/agent/tickets/4543

"I cannot seem to be able to access the DCF for the following. Please advise.

Single audit summary
Oregon Primary Care Association

UEI: KAM4HNCW7XC5

Report ID: 2023-03-GSAFAC-0000000334

FAC acceptance date: Dec. 4, 2023

Fiscal Year: April 1, 2022 to March 31, 2023"

Steps to reproduce the bug

Search using the UEI on the fac.gov site
Click on View
Try to download the SF-SAC by clicking on the download button

Expected Behavior

Should be able to download the SF-SAC but it is greyed out

Screenshots

No response

System setup

No response

Additional context

No response

Code of Conduct

• I agree to abide by the Digital.gov Community Guidelines and the TTS Code of Conduct. Respect your peers, use plain language, and be patient.
• I checked the current issues for duplicate bug reports.

[phildominguez-gsa]

This issue occurs when a submission has zero federal awards (Slack discussion here). This is because the button becomes disabled if no entries can be found in DisseminationCombined. This materialized view is refreshed nightly, so the idea for this check was to prevent users from downloading empty SF-SACs before they get a chance to be populated. @danswick @jadudm Maybe we could enable the button if an entry exists in DisseminationCombined OR if it's been > 24h since their submission time?

[phildominguez-gsa]

See dev discussion notes for 2024-9-11 (#6) for next steps

[danswick]

From some prior notes:

We probably need to treat these like the “five stuck SACs” from days of yore: find all cases of 0 federal awards, reach out to everyone to let them know their reports are incorrect, present options.

This report ID is related to the "five stuck SACs" except that it came in so early that we didn't have the validations in place that would later cause the "stuckness." Instead, this report made it all the way through to dissemination without any federal awards.

edit: turns out we're tracking this same report ID here as well: #4394