SigNoz/signoz · error

encountered multiple errors: %s

Error message

encountered multiple errors: %s

What it means

runWindowBasedListQuery executes GetListResultV3 per time window; if a single window's query fails, it wraps that error with multierr and returns immediately with a per-query error map containing the offending query name.

Source

Thrown at pkg/query-service/app/querier/querier.go:396

		if isLogs {
			// for logs we use limit to define the absolute limit and pagesize to define the current limit
			params.CompositeQuery.BuilderQueries[qName].PageSize = limitWithOffset
		} else {
			params.CompositeQuery.BuilderQueries[qName].Limit = limitWithOffset
		}

		queries, err := q.builder.PrepareQueries(params)
		if err != nil {
			return nil, nil, err
		}
		for name, query := range queries {
			rowList, err := q.reader.GetListResultV3(ctx, query)
			if err != nil {
				errs := []error{err}
				errQueriesByName := map[string]error{
					name: err,
				}
				return nil, errQueriesByName, fmt.Errorf("encountered multiple errors: %s", multierr.Combine(errs...))
			}
			length += uint64(len(rowList))

			// skip the traces unless offset is 0
			for _, row := range rowList {
				if offset == 0 {
					data = append(data, row)
				} else {
					offset--
				}
			}
		}

		limitWithOffset = limitWithOffset - length

		if isLogs && uint64(len(data)) >= pageSize {
			// for logs
			break

View on GitHub (pinned to 5069bf80b0)

Solutions

  1. Read the wrapped multierr message for the underlying ClickHouse error and the errQueriesByName map for the query name
  2. Shrink the requested time range so individual windows are cheaper
  3. Check query-service logs for the exact SQL and ClickHouse error; verify schema/upgrade state
  4. Retry after transient ClickHouse issues (connection resets, restarts)
Defensive patterns

Strategy: retry

Try / catch

if err != nil && strings.Contains(err.Error(), "encountered multiple errors") {
    if isTransientClickHouseErr(err) { time.Sleep(backoff); retry() }
}

Prevention

When it happens

Trigger: QueryRange on a List panel (traces/logs) where the ClickHouse SQL for one window fails: schema errors, timeouts, connection loss mid-pagination.

Common situations: Timeout on a large window because start/end per window are wide, ClickHouse restart during pagination, version mismatch where generated SQL references missing columns.

Related errors


AI-assisted analysis of SigNoz/signoz@5069bf80b0 (2026-08-28). Data as JSON: /api/errors/85486fac2d6ca352. Report an issue: GitHub.