You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All documentation (including here and here) suggests that the GetMetricDataV2 Connect command supports a historical metric named CONTACTS_QUEUED_BY_ENQUEUE, however, the HistoricalMetricName enum does not contain that metric here.
Having this metric name added to the exported enum will help me write cleaner, more robust code in my app.
Regression Issue
Select this option if this issue appears to be a regression.
SDK version number
@aws-sdk/client-connect@3.717.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
n/a
Reproduction Steps
n/a
Observed Behavior
Supported metric is not present in the enum of metric names
Expected Behavior
Supported metric is present in the enum of metric names
Possible Solution
Add all supported metrics to the enum of metric names
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered:
Checkboxes for prior research
Describe the bug
All documentation (including here and here) suggests that the GetMetricDataV2 Connect command supports a historical metric named
CONTACTS_QUEUED_BY_ENQUEUE
, however, theHistoricalMetricName
enum does not contain that metric here.Having this metric name added to the exported enum will help me write cleaner, more robust code in my app.
Regression Issue
SDK version number
@aws-sdk/client-connect@3.717.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
n/a
Reproduction Steps
n/a
Observed Behavior
Supported metric is not present in the enum of metric names
Expected Behavior
Supported metric is present in the enum of metric names
Possible Solution
Add all supported metrics to the enum of metric names
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: