no function clause matching in Commanded.Commands.Dispatcher.telemetry_stop/3

We are getting the following issue:

FunctionClauseError: no function clause matching in Commanded.Commands.Dispatcher.telemetry_stop/3
  File "lib/commanded/commands/dispatcher.ex", line 214, in Commanded.Commands.Dispatcher.telemetry_stop/3
  File "lib/commanded/commands/dispatcher.ex", line 59, in Commanded.Commands.Dispatcher.dispatch/1
  File "lib/myapp/balances_updater.ex", line 25, in MyApp.BalancesUpdater.handle_message/3
  File "lib/broadway/topology/processor_stage.ex", line 159, in anonymous fn/6 in Broadway.Topology.ProcessorStage.handle_messages/4
  File "/opt/app/deps/telemetry/src/telemetry.erl", line 320, in :telemetry.span/3
  File "lib/broadway/topology/processor_stage.ex", line 146, in Broadway.Topology.ProcessorStage.handle_messages/4
  File "lib/broadway/topology/processor_stage.ex", line 65, in anonymous fn/2 in Broadway.Topology.ProcessorStage.handle_events/3
  File "/opt/app/deps/telemetry/src/telemetry.erl", line 320, in :telemetry.span/3

Arguments:

arg0: {:error, :too_many_attempts}
arg1: -576084594885863171
arg2: %{application: MyApp, error: nil, execution_context: %Commanded.Aggregates.ExecutionContext{command: %MyApp.UpdateBalances{...}}

Start in lib/commanded/commands/dispatcher.ex at telemetry_stop/3 and trace how dispatch/1 reaches it. Reproduce or inspect the reported arguments, especially {:error, :too_many_attempts}, and determine the expected telemetry stop path. Done means the reported dispatch flow no longer raises FunctionClauseError and relevant behavior is covered by the project's existing tests.