weaviate/weaviate · error

no params provided

Error message

no params provided

What it means

Returned by the sum-transformers module's _additional {summary} property function when the caller supplies no Params (nil) for the summarization additional property. The module needs user-supplied parameters (which properties to summarize) to operate, so a nil params pointer is treated as a programming/configuration error rather than silently returning results.

Source

Thrown at modules/sum-transformers/additional/summary/summary_result.go:31

import (
	"context"
	"errors"
	"fmt"

	"github.com/weaviate/weaviate/entities/models"
	"github.com/weaviate/weaviate/entities/search"
	"github.com/weaviate/weaviate/modules/sum-transformers/ent"
)

func (p *SummaryProvider) findSummary(ctx context.Context,
	in []search.Result, params *Params,
) ([]search.Result, error) {
	if len(in) == 0 {
		return nil, nil
	} else {
		if params == nil {
			return nil, fmt.Errorf("no params provided")
		}

		properties := params.GetProperties()

		// check if user parameter values are valid
		if len(properties) == 0 {
			return in, errors.New("no properties provided")
		}

		for i := range in { // for each result of the general GraphQL Query
			ap := in[i].AdditionalProperties
			if ap == nil {
				ap = models.AdditionalProperties{}
			}

			// check if the schema of the GraphQL data object contains the properties and they are text or string values
			textProperties := map[string]string{}
			schema := in[i].Object().Properties.(map[string]interface{})

View on GitHub (pinned to 75aa4b6d11)

Solutions

1. Add the required parameters to the _additional summary block in the GraphQL query, e.g. _additional{summary{properties:["text"]}}
2. Upgrade the client/Weaviate version so summary parameters are correctly serialized into the query
3. Check that the sum-transformers module is properly configured and enabled (ENABLE_MODULES=sum-transformers) with a reachable inference container
4. Inspect the constructed GraphQL query for missing/dropped summary arguments

Example fix

// before
{ Get { Article { _additional { summary { path } } } } }
// after
{ Get { Article { _additional { summary { properties: ["body"] } } } } }

// construct the GraphQL query with required summary params
query := `
{ Get { Article { _additional {
  summary { properties: ["body"] }
} } } }`
_ = query // send via client.Query()

res, err := graphqlClient.Query(ctx, query)
if err != nil {
	if strings.Contains(err.Error(), "no params provided") {
		// rebuild the query including summary{properties:[...]}
	}
	return err
}

When it happens

Trigger: A GraphQL query requests _additional{summary{...}} but the module's parameter extraction yields nil — typically when summary parameters are absent or the module wiring passes nil params into findSummary.

Common situations: Querying the summary additional property without providing the required arguments (e.g. properties); module misconfiguration where the summary parameters are stripped by an intermediate client/GraphQL layer; older clients constructing the additional property programmatically without params.

Understand the failure class

Background: "missing required argument" and "the following required arguments were not provided": what required-argument errors mean and how to fix them — this error's family across 20 libraries.

Related errors

• no properties provided
• failed to parse summarization response (status %d): %w
• no groups found in aggregate result
• Unknown aggregation type ${aggType}
• unknown aggregation type ${aggType}

AI-assisted analysis of weaviate/weaviate@75aa4b6d11 (2026-09-04). Data as JSON: /api/errors/81dff85b6fadfb3b. Report an issue: GitHub.