What validations should I perform when negative time values appear in the $mints_last_call variable of the "Last Agent" component?
You will learn to identify and solve problems related to negative values in the $mints_last_call variable of the Last Agent component.
Table of Contents
Symptom / Need
During queries or tests on the "Last Agent" component, the component works actively and returns information to the user, but the time value returned by the $minutes_last_call variable is generated or printed as a negative number.
Context / Scenarios
This new feature is directly displayed in the " Last Agent " component, located within the Statistics tab of the Agentic Engine in the RP (routing point). This behavior is present across all service channels.
Answer / Solution
Step 1: Initial Validations and Tests in the Environment
- Keep in mind the ID or Name of the Routing Point or flow where you have configured the component.
- Upon entering the Routing Point, go to the Statistics tab and verify that the Search last agent 24h component is correctly configured.
- Check the behavior and output of the $minuts_last_call variable.

- Perform validation tests on the different routing flows (Voice, Chat, Interactions).
- Set up a test flow using the Find Last Agent 24h component, perform an initial interaction through the flow, and end it.
- Subsequently, it performs a second iteration and validates the value that the variable $minuts_last_call is returning, in order to determine whether or not it is correct.
If the problem persists, escalate the case to the Wolkvox service desk.
- If the case is escalated to the service desk, the Level 1 analyst: Repeats steps 5 and 6 on a different server operation.
- The service desk analyst checks if any updates were deployed on the server, which could have affected the component's proper functioning.
Step 2: Incident Generation and Technical Escalation
- Upon discovering that the variable $minuts_last_call generates negative values, proceed to create a specific incident for the analysis of this parameter.
- Escalate the case directly to Level 3 (Core Team) in order to perform the technical analysis and apply the adjustment to the information returned by the component.
Escalation
Minimum Information / Evidence Required for Escalation
To escalate the case correctly, you must gather the following evidence:
- Graphical evidence of the configuration of the "Last Agent" component in the Statistics tab.
- Display or screenshot showing the negative time values generated by the $minuts_last_call variable.

- Evidence and results of the tests performed on the different routing flows, specifying the channel in which the novelty is occurring.
- Date from which the component shows damage.
With this information, the case will be escalated to Level 3 (Core Team).