Difference between revisions of "ATC/Current/AdminGuide/MonitorArchFlows"

From Genesys Documentation
Jump to: navigation, search
(Published)
m (Text replacement - "Genesys Cloud" to "Genesys Cloud CX")
 
(12 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
|TocName=Monitor
 
|TocName=Monitor
 
|Context=Monitor an action map that uses an Architect flow action to evaluate how well it's working.
 
|Context=Monitor an action map that uses an Architect flow action to evaluate how well it's working.
 +
|Dimension=ArchFlow
 
|ComingSoon=No
 
|ComingSoon=No
−
|Platform=PureEngage, PureConnect, PureCloud
+
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 
|Prereq='''Prerequisites'''
 
|Prereq='''Prerequisites'''
  
−
*[https://help.mypurecloud.com/articles/altocloud-permissions-overview Configure the following permissions in PureCloud:]
+
*[https://help.mypurecloud.com/articles/?p=195191 Configure the following permissions in Genesys Cloud CX:]
−
**'''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)
 
|Section={{Section
 
|Section={{Section
Line 15: Line 16:
 
|anchor=MonitorArchFlow
 
|anchor=MonitorArchFlow
 
|alignment=Vertical
 
|alignment=Vertical
−
|Media=
+
|structuredtext=Use the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_Map_Performance|display text=Action Map reports}} 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.<font color="#ff0000"></font>
−
|image=
 
−
|structuredtext=Use the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=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.<font color="#ff0000"></font>
 
 
{{{!}} class="wikitable" style="width: 1205px;"
 
{{{!}} class="wikitable" style="width: 1205px;"
 
{{!}}-
 
{{!}}-
Line 31: Line 30:
 
{{!}}-
 
{{!}}-
 
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Accepted'''
 
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Accepted'''
−
{{!}} style="width: 961.047px;"{{!}}Number of times the Architect flow connected with the third-party product is initiated.
+
{{!}} style="width: 961.047px;"{{!}}Number of times that the Architect flow connected with the third-party product.
 
{{!}}-
 
{{!}}-
 
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Started'''
 
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Started'''
Line 40: Line 39:
 
{{!}}-
 
{{!}}-
 
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Rejected'''
 
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Rejected'''
−
{{!}} style="width: 961.047px;"{{!}}Number of times PureCloud rejected the Architect flow's request because the request was wrong. This can happen because of two possible scenarios:
+
{{!}} style="width: 961.047px;"{{!}}Number of times that Genesys Cloud CX rejected the Architect flow's request because the request was wrong. The rejection can occur in the following scenarios:
  
−
*The Architect flow no longer exists.
+
*Architect flow no longer exists.
−
*The data required to launch the Architect flow has not been provided.
+
*Data required to launch the Architect flow wasn't provided.
−
*The action map is firing intensively and exceeding the PureCloud rate limits (more than 15 requests/second). Requests will not be retried once the throttling threshold is exceeded.
+
*Action map is firing intensively and exceeding the Genesys Cloud CX rate limits (more than 15 requests/second). Requests aren't retried once they exceed the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=How_throttling_works|display text=throttling}} threshold.
 
{{!}}-
 
{{!}}-
 
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Errored'''
 
{{!}} style="width: 219.953px;"{{!}}'''Web Actions Errored'''
Line 52: Line 51:
 
{{!}} style="width: 961.047px;"{{!}}Not applicable.
 
{{!}} style="width: 961.047px;"{{!}}Not applicable.
 
{{!}}}
 
{{!}}}
−
|structuredtextwide=
 
−
|FAQHeading=
 
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Latest revision as of 21:27, November 9, 2021

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

Monitor an Architect flow action's performance

Use the Action Map reports 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 that the Architect flow connected with the third-party product.
Web Actions Started Not applicable.
Web Actions Engaged Not applicable.
Web Actions Rejected Number of times that Genesys Cloud CX rejected the Architect flow's request because the request was wrong. The rejection can occur in the following scenarios:
  • Architect flow no longer exists.
  • Data required to launch the Architect flow wasn't provided.
  • Action map is firing intensively and exceeding the Genesys Cloud CX rate limits (more than 15 requests/second). Requests aren't retried once they exceed the throttling threshold.
Web Actions Errored Number of times the web action request resulted in an error.
Web Actions Timed out Not applicable.
Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/MonitorArchFlows (2025-06-22 15:46:38)"
Comments or questions about this documentation? Contact us for support!