The one I figure is the problematic one is that one about returns for 2019 being "not fully processed"... that could mean a lot of different things. It's not just one program and likely not just one system that "processes" a tax return.
And who knows what all this query system they threw together looks at. A flat file, but probably not from just one data extract. So there would probably be a bunch of extract programs that funnel stuff into some other program that creates that one big flat file with "everything" in it. And when "everything" is not in it yet, the query program says "status unavailable". That program won't know enough to refine the error message; it's not going to know whether there's a reason for some data value to be zero or null, or whether it's just that way because a feeder program hasn't run yet, or because there's a bug in one of the feeder programs and it's not enough of a bug to universally affect the output in noticeable ways.
And who knows what all this query system they threw together looks at. A flat file, but probably not from just one data extract. So there would probably be a bunch of extract programs that funnel stuff into some other program that creates that one big flat file with "everything" in it. And when "everything" is not in it yet, the query program says "status unavailable". That program won't know enough to refine the error message; it's not going to know whether there's a reason for some data value to be zero or null, or whether it's just that way because a feeder program hasn't run yet, or because there's a bug in one of the feeder programs and it's not enough of a bug to universally affect the output in noticeable ways.
