Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

[BUG] Messages sent via routeMessageByChannelId are not shown in the source channel Dashboard

Aberta
  • Algo errado?
#402 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
42/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
java
Domínio
backend, observability

Direção de pesquisa

Start from the routeMessageByChannelId() API used in channel transformer/destination scripts and how routed messages are stored versus how the source channel Dashboard lists messages. Reproduce with two channels as in the issue: send one message on the source, confirm it appears on target Dashboards but not the source. Done when source-channel Dashboard (or a dedicated routed-messages view) shows those internally routed messages so source-side monitoring matches downstream processing.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

bug

Describe the bug
When a channel sends messages internally using routeMessageByChannelId(), those routed messages are processed by target channels but are not shown in the source channel Dashboard.

Steps to reproduce the behavior:

  • Create Channel A (source) and Channel B/Channel C (targets).
  • In Channel A transformer/destination script, call routeMessageByChannelId() for Channel B and Channel C.
  • Deploy channels.
  • Send one message to Channel A.
  • Let Channel A route internally to Channel B and Channel C via routeMessageByChannelId().
  • Open Dashboard for Channel B and Channel C.
  • Observe routed messages are shown there.
  • Open Dashboard for Channel A.
  • Observe the routed messages are not shown in Channel A Dashboard.

Expected behavior

  • Messages sent via routeMessageByChannelId() should be shown in the source channel Dashboard, or there should be a dedicated Dashboard view that clearly shows routed messages initiated by the source channel.

Actual behavior:
Routed messages are shown in Dashboard for Channel B and Channel C, but the same routed messages are not shown in Channel A Dashboard.

Environment
OS: Linux
Java Distribution/Version: OpenJDK 17
Connect Version: 4.5.2

Additional context
This creates an observability gap: downstream processing confirms routing occurred, but source channel Dashboard does not reflect those routed messages, making source-side operational monitoring misleading.

Linguagem predominante
Java
Estrelas
227
Forks
81
Merge médio
3d 6h
PRs com merge (30d)
15

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de OpenIntegrationEngine/engine

Todas as issues de OpenIntegrationEngine/engine

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.