hashicorp/nomad · error

failed to lookup related evals: %v

Error message

failed to lookup related evals: %v

What it means

Fires inside Eval.Get when IncludeRelated is set and the state store query for evaluations related to the requested eval fails — a state store read error while gathering the eval's related evaluations.

Source

Thrown at nomad/eval_endpoint.go:90

			var related []*structs.EvaluationStub

			// Look for the eval
			eval, err := state.EvalByID(ws, args.EvalID)
			if err != nil {
				return fmt.Errorf("failed to lookup eval: %v", err)
			}

			if eval != nil {
				// Re-check namespace in case it differs from request.
				if !allowNsOp(aclObj, eval.Namespace) {
					return structs.ErrPermissionDenied
				}

				// Lookup related evals if requested.
				if args.IncludeRelated {
					related, err = state.EvalsRelatedToID(ws, eval.ID)
					if err != nil {
						return fmt.Errorf("failed to lookup related evals: %v", err)
					}

					// Use a copy to avoid modifying the original eval.
					eval = eval.Copy()
					eval.RelatedEvals = related
				}
			}

			// Setup the output.
			reply.Eval = eval
			if eval != nil {
				reply.Index = eval.ModifyIndex
			} else {
				// Use the last index that affected the evals table
				index, err := state.Index("evals")
				if err != nil {
					return err
				}

View on GitHub (pinned to 482b49bf1a)

Solutions

1. Inspect server logs for state store errors
2. Retry the query; transient read failures usually resolve
3. Drop IncludeRelated if only the eval itself is needed

When it happens

Trigger: Thrown at nomad/eval_endpoint.go:90 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of hashicorp/nomad@482b49bf1a (2026-09-04). Data as JSON: /api/errors/a4150a9849951638. Report an issue: GitHub.