Anyone? I noticed that when I make a call with ‘fields’ parameter including all important fields except ‘checkItemStates’, the error disappears. Earlier I have been calling simply ‘?fields=all’.
I noticed that the ‘checkItemStates’ is null regardless if I have a checklist with a mix of completed/open items on the given card or no checklists at all. It seems strange to me to throw an error when due to using a field that is always ‘null’.
Are you having a bug there? Could you investigate and potentially update your API, so calling this API, with ‘?fields=all’ does not pose a risk of throwing this sort of errors in the future?