platform-request-timeout
Section: default
Default Value: 5000
Valid Values: Any nonnegative integer
Changes Take Effect: On the next interaction
Introduced: 9.0.017.01
The timeout duration, in milliseconds, specifying how long Universal Routing Server (URS) should wait for a response from the GPR Core Platform after a GPR subroutine makes a request that the routing strategy sends to the GPR Core Platform. After this timeout expires, the subroutine logs a GPR error and URS continues to process the strategy.
This option overrides the URS request_timeout option, which has a default value of 0. If the default value is set for timeout_response and, for some reason, GPR Core Platform does not respond correctly, URS waits indefinitely instead of proceeding with the strategy and the interaction is not routed.
9.0.017.01
Predictive Routing - URS Strategy Subroutines Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 07/28/20 | General | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- The new platform-request-timeout configuration option enables you to set a timeout, after which the GPR Core Platform sends Universal Routing Server (URS) a timeout response, which prompts URS to continue processing the strategy. This option overrides the URS request_timeout option, which has a default value of 0. Previously, if the default value was set for timeout_response and, for some reason, GPR Core Platform did not respond correctly, URS waited indefinitely instead of proceeding with the strategy and the interaction was not routed. (PRR-6229)
Resolved Issues
This release contains the following resolved issues:
- Added CallUUID in score request sent to GPR from strategy.
# Added CallUUID_RPVQID in score_log request (PRR-6558)
see description (PRR-6390)
The URS Strategy Subroutines now correctly terminates scoring requests for predictors that have no customer features are available and provides informative results to the Genesys Info Mart database and to the GPR score-log. Predictors must have at least one customer featured configured to enable scoring.
In this scenario, the URS Strategy Subroutines sends the following two KVPs to the Genesys Info Mart database and to the GPR score-log: gpmResult = 7 and gpmMessage = "Failed to build Scoring Context". (PRR-6233)
Upgrade Notes
No special procedure is required to upgrade to release 9.0.017.01.