@sharedcodingsans we did upgrade our GraphQL engine, yes. We performed one week of inspection on 50% of the total of queries made to the system (that’s about 20M+ requests) to see if there was any different behavior between the old and the new version. For each of these inconsistencies, we logged the project IDs, the precise queries performed and the number of queries.
Apart from minor nuances in how errors are reported, we found three notable differences (all bugfixes to make our responses more compliant to GraphQL standard), including the one you encountered.
For two of these three inconsistencies — not the one you experienced, unfortunately — we managed to still keep the old behavior in place, and just respond with a
X-DatoCMS-Warnings header for the foreseeable future. Unfortunately, for the third change (the one you experienced), we could not do that for technical reasons.
Less than 0.0001% of the queries (around 10 projects) had the “empty attribute list” error, so we decided to contact every project owner personally via e-mail to inform them about the change, and we made sure the upgrade didn’t cause any problems.
We then decided it was a more than a statistically significant number to proceed with the upgrade.
All this is to say that we tried to do everything as seamless as possible, and in general we succeeded, but evidently, despite extensive testing, we missed a few cases. To date, after weeks from the engine upgrade, in addition to yours we have received a second complaint for the same issue.
I’m very sorry about this, and we’ll try to adopt an even safer process next time.