A change to internal schema definitions accidentally broke querying on datasets that contain non-trace data. Queries sent during that time would have seen errors stating "Something went wrong." We have reverted the changeset in question and queries should be back to normal. Other functionalities were not impacted.