Time Entity Not Recognized in Universal Bot but Works in Child Bot

I have a Universal Bot with several child bots linked to it. One of these child bots is a Job-related Bot, which contains a dialogue task named “Reschedule Job with Assignment”.

Issue:

The time entity is not being recognized when the utterance is processed in the Universal Bot, but it works correctly in the Job-related Bot.

Example Utterance:

“Reschedule Job 155917 to tomorrow 11AM and assign it to 0001”

Expected Entity Recognition:

  • 155917 → Job Number (number)
  • tomorrow → Date (date)
  • 11AM → Time (time) (Not recognized in Universal Bot)
  • 0001 → Tech ID (number)

Observations:

  • The time entity is correctly recognized when the utterance is processed directly in the Job-related Bot.
  • However, in the Universal Bot, the time entity is not being detected while other entities (job number, date, tech ID) are recognized properly.

Question:

What could be causing the time entity to not be recognized in the Universal Bot? Are there any specific configurations or entity propagation settings that I should check?

please find the screenshot of NL Analysis of universal bot and utterance training