Difference between revisions of "ATC/Current/AdminGuide/MonitorArchFlows"
From Genesys Documentation
m (Text replacement - "\|Platforms?=([^\|]*)PureCloud([\|]*)" to "|Platform=$1GenesysCloud$2") |
m (Text replacement - "PureCloud" to "Genesys Cloud") |
||
| Line 8: | Line 8: | ||
|Prereq='''Prerequisites''' | |Prereq='''Prerequisites''' | ||
| − | *[https://help.mypurecloud.com/articles/altocloud-permissions-overview Configure the following permissions in | + | *[https://help.mypurecloud.com/articles/altocloud-permissions-overview Configure the following permissions in Genesys Cloud:] |
**'''Journey '''> ''' Report''' > '''View''' | **'''Journey '''> ''' Report''' > '''View''' | ||
**'''Journey '''>''' Action Map '''> '''View''' (to see action maps in the report) | **'''Journey '''>''' Action Map '''> '''View''' (to see action maps in the report) | ||
| Line 40: | Line 40: | ||
{{!}}- | {{!}}- | ||
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Rejected''' | {{!}} style="width: 219.953px;"{{!}}'''Web Actions Rejected''' | ||
| − | {{!}} style="width: 961.047px;"{{!}}Number of times | + | {{!}} style="width: 961.047px;"{{!}}Number of times Genesys Cloud rejected the Architect flow's request because the request was wrong. This can happen because of two possible scenarios: |
*The Architect flow no longer exists. | *The Architect flow no longer exists. | ||
*The data required to launch the Architect flow has not been provided. | *The data required to launch the Architect flow has not been provided. | ||
| − | *The action map is firing intensively and exceeding the | + | *The action map is firing intensively and exceeding the Genesys Cloud rate limits (more than 15 requests/second). Requests will not be retried once the throttling threshold is exceeded. |
{{!}}- | {{!}}- | ||
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Errored''' | {{!}} style="width: 219.953px;"{{!}}'''Web Actions Errored''' | ||
Revision as of 12:05, July 15, 2020
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Monitor an action map that uses an Architect flow action to evaluate how well it's working.
Prerequisites
- Configure the following permissions in Genesys Cloud:
- Journey > Report > View
- Journey > Action Map > View (to see action maps in the report)
Monitor an Architect flow action's performance
Use the Action map performance to monitor your Architect flow action's performance. When you create an action map that uses an Architect flow action, the metric names have different meanings.
| Metric | Description |
| Web Actions Qualified | Number of visitors who matched a segment, activity, or outcome score that triggered the action map. |
| Web Actions Offered | Not applicable. |
| Web Actions Accepted | Number of times the Architect flow connected with the third-party product is initiated. |
| Web Actions Started | Not applicable. |
| Web Actions Engaged | Not applicable. |
| Web Actions Rejected | Number of times Genesys Cloud rejected the Architect flow's request because the request was wrong. This can happen because of two possible scenarios:
|
| Web Actions Errored | Number of times the web action request resulted in an error. |
| Web Actions Timed out | Not applicable. |
Comments or questions about this documentation? Contact us for support!