Right filter, wrong sibling

An AWS account running on credits reports a bill of nothing. Unfiltered, Cost Explorer nets to zero dollars, which is accurate and useless. So usage queries filter out credits and refunds, and the credits are fetched separately.

The same filter went onto the forecast call too.

The forecast already ignores credits. Filtering them out a second time moved the forecast from 5.66 dollars to 36.50.

Nothing failed. A number came back, with decimals, and looked like the other numbers.

Two calls that sit next to each other in the documentation do not have to agree about what they count.