Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#402 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
java
Área
backend, observability

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Java
Estrellas
227
Forks
81
Merge medio
3 d 15 h
PR fusionados (30 d)
13

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenIntegrationEngine/engine

Todos los issues de OpenIntegrationEngine/engine

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.