✅ Note: Only applies if “Persistent RONA” is enabled via Distribution Service Settings.

• When the target User is already is in RONA state.
  ⮑ A message will be shown after a transfer attempt is made: “Transfer cannot be started to a User, who is in a Nimbus Task”. 
  ⮑ There will be no extra User Session for Nimbus Reporting created.²
• When the target User ignores / doesn't answer the transfer (e.g. Timeout), Nimbus will not flag users with RONA state¹.
  ⮑ User Session in Nimbus Reporting marked “Cancelled”²
• When the target User actively declines a transfer will also not flag users with RONA state. 
  ⮑ User Session in Nimbus Reporting marked as “Declined”.²

¹🤔 Why is RONA not applied in this case? When a User is a direct transfer target, they were not selected by the Nimbus Task Queue and Distribution system. In order to keep that user available to other Nimbus Services – e.g. after previous transfer / timeout – no persistent RONA state is applied.
² Depending on the Attendant Console transfer scenario (safe/blind), the call will return to the initial User or be lost. This is not related to RONA behavior.