“The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.”

So it looks like there are three filters when filtering this report:
gwfWfTaskStatus, in this case being filtered by "Created"
gwfWfTaskSk, in this case being filtered by not null, and
gwfWfSk. In this case, it looks like gwfWfSk is being filtered against the entire possible range of workflows (numbers ranging from 22 up to 8829).

Would it be possible to remove this filter, test, and see if that helps? Rather than explicitly saying "filter against this value being part of workflow 1 or 2 or 3 or 4, etc" through the entire set of values, just have that implicitly set by not specifying any workflows to be part of. This should still query against the whole range of workflows.

So it looks like there are three filters when filtering this report:
gwfWfTaskStatus, in this case being filtered by "Created"
gwfWfTaskSk, in this case being filtered by not null, and
gwfWfSk. In this case, it looks like gwfWfSk is being filtered against the entire possible range of workflows (numbers ranging from 22 up to 8829).

Would it be possible to remove this filter, test, and see if that helps? Rather than explicitly saying "filter against this value being part of workflow 1 or 2 or 3 or 4, etc" through the entire set of values, just have that implicitly set by not specifying any workflows to be part of. This should still query against the whole range of workflows.