Error: trajectory converted to zero chat messages

Getting this over and over again. The form on the feedback page just clears when submitting without any indication if it was sent or not. Leaving this here in the hopes this might get to the right people:

Trajectory ID: b76e1a4f-406f-4386-bf6e-fd7872460c20
Error: trajectory converted to zero chat messages
(1) attached stack trace
  -- stack trace:
  | google3/third_party/gemini_coder/framework/generator/generator.(*requestBuilder).buildRequest
  | 	third_party/gemini_coder/framework/generator/request_builder.go:122
  | google3/third_party/gemini_coder/framework/generator/generator.(*PlannerGenerator).generateWithAPIRetry
  | 	third_party/gemini_coder/framework/generator/planner_generator.go:269
  | google3/third_party/gemini_coder/framework/generator/generator.(*PlannerGenerator).generateWithModelOutputRetry
  | 	third_party/gemini_coder/framework/generator/planner_generator.go:154
  | google3/third_party/gemini_coder/framework/generator/generator.(*PlannerGenerator).Generate
  | 	third_party/gemini_coder/framework/generator/planner_generator.go:95
  | google3/third_party/gemini_coder/framework/executor/executor.(*Executor).Execute
  | 	third_party/gemini_coder/framework/executor/executor.go:303
  | google3/third_party/jetski/cortex/cortex.(*CascadeManager).executeHelper.func1
  | 	third_party/jetski/cortex/cascade_manager.go:1558
  | google3/third_party/jetski/cortex/cortex.(*CascadeManager).executeHelper.func2
  | 	third_party/jetski/cortex/cascade_manager.go:1676
  | runtime.goexit
  | 	third_party/go/gc/src/runtime/asm_arm64.s:1447
Wraps: (2) trajectory converted to zero chat messages
Error types: (1) *withstack.withStack (2) *errutil.leafError
1 Like

Hi @ottomatic ,

The error “trajectory converted to zero chat messages” indicates that while the Planner successfully received the request, the message content was either missing or filtered out during preprocessing, leaving the Generator with no input to process.
To help us diagnose the issue, could you please answer the following:

  • Does this happen on every prompt or only certain ones?
  • Are you using a custom workflow or slash command when it occurs?
  • Did this start after a recent update?