Bug Report: Interview Goodbye Message Repeated Three Times 

Summary
During a maintenance worker interview session, the closing “thank you / goodbye” message is displayed three times in a row instead of once. This leads to a confusing and unprofessional user experience for the respondent and suggests an underlying backend or orchestration issue.

Context

• Environment: Staging (ontora-r25igzwc0.staging.ontora.com)

• Flow: Maintenance interview, Topic 1 of 4 – “Typical Job Workflow”

• Persona: “Max” (maintenance worker)

• Affected area: Conversation orchestration and message rendering at the end of an interview

Observed Behavior
At the end of the interview, the assistant produces three different goodbye / thank-you variants sequentially:

1. “Thanks so much, Max. Your insights are really helpful and will make a difference. We appreciate you taking the time to share your experiences with us today.”

2. “Thank you so much for sharing your insights with me today. Your candid feedback is incredibly valuable and will really help us understand how to make improvements. I truly appreciate your time and honesty.”

3. “Thank you so much for sharing your time and insights with me today. Your perspective is incredibly valuable, and it will definitely help us make real improvements. I really appreciate your candor. Goodbye!”

All three appear as separate messages at the end of the same session.

Expected Behavior
Only a single, clear closing message should be sent at the end of the interview flow (either a fixed template or one selected deterministically), not multiple variants.

Impact

• Confusing experience for respondents; looks like the system is glitching or over-eager.

• Indicates potential defects in backend logic around step completion, message deduplication, or event handling (e.g., multiple “end of flow” triggers).

• Could hint at deeper issues in conversation state management, such as duplicated events, idempotency gaps, or race conditions.

Initial Hypotheses (Backend Focus)

• Multiple “conversation completed” events emitted and each triggers a separate closing message.

• Retry logic without idempotency key causing the closing step to execute multiple times.

• Misconfigured flow definition with three different closing nodes all reachable from the same terminal state.

• Race condition between streaming / completion handlers that each append a goodbye.

Recommended Backend Investigation

• Inspect logs for the affected session ID:

  • How many “flow_end” / “conversation_completed” events were emitted?

  • How many calls to the “closing message” generation function occurred?

• Verify flow configuration for this interview template:

  • Ensure there is exactly one terminal node and one closing