Closed cugarteblair closed 1 year ago
This was due to hacking the mostrecent<charge/credit/recon>_time to force a one-time recalculation when delivering new code with a change to recon logic. There is a hard coded 8 hour throttle on getting new data from the cost explorer so once the dates were updated when new cost data was received things were back to normal.
forecast page dates are off by one year