WikiSysop: Created page with "{{ComponentRN |ComponentId=b9e5e9d4-37a0-4fa2-87a3-957773249c9b |JQL=labels=DESRN10002110001 |DeploymentTypeId=5439f1be-1868-4091-b058-1667389b6ce1 |ReleaseDate=2023-12-08 |Hi..."

2023-12-06T18:00:25Z

Created page with "{{ComponentRN |ComponentId=b9e5e9d4-37a0-4fa2-87a3-957773249c9b |JQL=labels=DESRN10002110001 |DeploymentTypeId=5439f1be-1868-4091-b058-1667389b6ce1 |ReleaseDate=2023-12-08 |Hi..."

New page

{{ComponentRN
|ComponentId=b9e5e9d4-37a0-4fa2-87a3-957773249c9b
|JQL=labels=DESRN10002110001
|DeploymentTypeId=5439f1be-1868-4091-b058-1667389b6ce1
|ReleaseDate=2023-12-08
|Highlight=Resolved issue.
}}
{{Issue
|TicketNumber=DES-14617
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Route Call block in Designer will now wait for up to 5 seconds before proceeding with the next block under certain circumstances on {{Azure}}. Behavior on {{AWS}} and {{Private Edition}} is unchanged. This change addresses a scenario observed on {{Azure}} under load in which Designer application fails to recognize the interaction has been routed and continues to run downstream blocks in {{Assisted Service}} instead of jumping to {{Finalize}}. After this fix, when this situation is encountered and the interaction has not been routed successfully by the time block timeout expires or the block is exited due to other conditions, the Route Call block will wait for up to 5 additional seconds to receive events from the platform related to routing attempts made from that block before proceeding with downstream blocks. E.g. if the next block is another routing block, it will be executed upto 5 seconds later than before and a milestone will be added to the SDR to indicate this situation has occurred {{Missing submit Ack}}. Note that this is rare scenario and application will behave normally after this fix and no corrective action is necessary from the application developer. Such SDRs may also show another milestone "{{Interaction routed on unknown request}}" which is normal.
|LocalContent=The Route Call block in Designer will now wait for up to ''5'' seconds before proceeding with the next block under certain circumstances on Azure. Behavior on AWS and Private Edition is unchanged. This change addresses a scenario observed on Azure, where under load, the Designer application fails to recognize that an interaction has been routed and continues to run downstream blocks in the <code>Assisted Service</code> phase instead of jumping to the <code>Finalize</code> phase. After this fix, when this situation is encountered and the interaction has not been routed successfully before the block timeout expires or the block is exited due to other conditions, the Route Call block will wait for up to ''5'' additional seconds to receive events from the platform, related to routing attempts made from that block before proceeding with the downstream blocks. For example, if the next block is another routing block, it will be executed upto ''5'' seconds later than before and a milestone, ''Missing submit Ack'', will be added to the SDR to indicate this situation has occurred. This is a rare scenario and the application will behave normally after this fix and no corrective action is necessary from the application developer. Such SDRs may also show another milestone, ''Interaction routed on unknown request'', which is normal.
}}

RN/Designer/100.0.211.0001 - Revision history

WikiSysop: Created page with "{{ComponentRN |ComponentId=b9e5e9d4-37a0-4fa2-87a3-957773249c9b |JQL=labels=DESRN10002110001 |DeploymentTypeId=5439f1be-1868-4091-b058-1667389b6ce1 |ReleaseDate=2023-12-08 |Hi..."