Common Issues with Queries | Honeycomb

Common Issues with Queries

If you need to troubleshoot querying in Honeycomb, explore these solutions to common issues.

Tip
To ask questions and learn more, visit our Support Knowledge Base or join our Pollinators Community.

Query Builder 

Troubleshoot issues related to Query Builder.

You receive a notice that fields were removed from your query 

When you select a new dataset, if the fields in the existing query do not exist in the new dataset, Honeycomb notifies you about the field(s) that were removed from your query.

Screenshot illustrating the informational message

If the fields should be available, make sure the fields in the old dataset exist in the new dataset.

Query Assistant 

Troubleshoot issues related to Query Assistant.

Query Assistant does not produce a query 

While we try to do our best to produce a query for a broad collection of input, we cannot guarantee a query for all inputs.

We recommend that you try to rephrase your input, or try using a different input.

Query Assistant takes a long time to produce a query 

Query Assistant relies on OpenAI’s API. An average response is under 5 seconds. A request with no response after 10 seconds likely indicates that compute resources for OpenAI’s API are unavailable for that request.

We recommend that you wait for a few seconds, and then try the request again.

Query Assistant returns different answers when you give it the same input 

Because Large Language Models (LLMs) are nondeterministic, Query Assistant may give a different answer for the same input. While we try to do our best to achieve a degree of consistency for similar inputs, we cannot guarantee the same query for the same input each time.

If you want to ensure you have a consistent query to run, we recommend saving a query to a board for later use.

Derived Columns 

Troubleshoot issues related to Derived Columns.

A Derived Column displays a null or unexpected value 

Null or unexpected values in Derived Columns are usually related to:

  • Mismatched field types. Many functions are sensitive to the input’s value type.

    Review the field types in the schema to ensure they align with the inputs of the functions. If necessary, coerce the fields with a cast operator function.

  • Name collisions. If data from an event sent to Honeycomb uses the same name as a Derived Column, the Derived Column takes priority over the data sent to Honeycomb.

    We recommend that you rename the field in your instrumentation or rename the Derived Column.

When a name collision occurs for a Derived Column, it may cause confusing behavior in Honeycomb. For example, links that use a duplicate field name may point to the wrong location.

Honeycomb requires that Derived Columns names be unique across their containing Environment. Derived Column names should not match the name of any other Derived Column or any other field in any Dataset contained within the Environment.

When you create a Derived Column in Honeycomb, we try to check that you have entered a display name that is unique to your Environment (although duplicate names can still occur). If the Derived Column exists before Honeycomb receives a field name with the same name, we allow both the pre-existing Derived Column and the new field with the duplicate name to exist, and we display a warning message in the Data Settings section of the UI under the Define Schema view.

To resolve this issue, check that your Derived Column names are unique and not already in use by a field in any Dataset in your Environment. If you find a duplicate name, we recommend renaming the Derived Column as soon as possible, making sure that the new name is unique to your Environment. If you unable to change the name of the Derived Column, then change your instrumentation to rename the field instead.

If you rename the field in your instrumentation, you must also delete it in Honeycomb. To do this, use the Column Deletion API. This method will prevent the column from being queried and remove the data in question from new query results, but it will not remove permalinks to existing queries that may contain this data. If you are a Pro/Enterprise user, you may also request help with deletion. Visit Honeycomb Support to create a ticket for our support team, or email support@honeycomb.io.