CLONE 2020R3 - Staging - Forecast Import not working

While performing the Smoke Test on Staging today, upgraded to 2020R2.1, I noticed that when trying to pull in a forecast from the Request AWS page, that it wouldn't work.
I have spent some more time on this, and it appears that the forecasts are not imported into the environment.
We upgraded last night and this seems to have started this morning.

I was investigating a similar, but maybe different, issue in JAT yesterday, CFAM-10826.

When running this SQL against Staging, I am seeing errors.

select * from tbAudit with(nolock)
where EventEntityID in (123, 1041)
and AuditDateTime > '2020-07-07'
and AuditCategoryID = 23
order by auditid

These are the error messages that I am seeing:

* Error getting or saving forecast data for 00198 from https://api.scforecast-test.cfadevelop.com/v1/forecast/status/00198?fromDate=07-15-2020&toDate=07-27-2020 to W:\Macromatix\SiteData\CFAStaging\DataImports\Forecast\Forecast_{storenumber}_{forecastdate}.xml: Can't Parse 0 as ForecastingSales
* Error getting or saving forecast data for 01919 from https://api.scforecast-test.cfadevelop.com/v1/forecast/status/01919?fromDate=07-15-2020&toDate=07-27-2020 to W:\Macromatix\SiteData\CFAStaging\DataImports\Forecast\Forecast_{storenumber}_{forecastdate}.xml: Can't Parse 0 as ForecastingSales

To try and determine if this was due to the non-production endpoint, or something on our side, I did swap over the endpoints to point at Prod, and it too failed, which makes me think that this is something in our code.

select * from tbAudit with(nolock)
where AuditID in (16380, 16381)

Note: this appears to be working in 2020R3 (Testing), but not in JAT (Trunk) and Staging (2020R2.1)