Description
The Conversation KPI "Generate KPI" functionality fails when processing dates in dd/MM/yyyy format.
When a date such as 14/08/2026 is provided, the Conversation KPI | Copy Transcripts (Child) flow fails while processing the date with the formatDateTime() function.
The flow returns the following error:
In function 'formatDateTime', the value provided for date time string '14/08/2026' was not valid. The datetime string must match ISO 8601 format.
This appears to be a date localization/formatting issue. The application provides the date using the regional dd/MM/yyyy format, while the child flow attempts to process that value directly as a datetime value.
The issue becomes especially noticeable from the 13th day of the month onward, because values such as 14/08/2026 cannot be interpreted as an alternative MM/dd/yyyy date.
Thank you for taking a look. Please let me know if any additional information or execution details would be helpful.
Steps to reproduce
- Open the Copilot Agent Kit.
- Go to an Agent Configuration configured for Conversation KPIs.
- Click Generate KPI.
- Provide a date using the dd/MM/yyyy regional format, for example 14/08/2026.
- Run the KPI generation.
- Open the execution history of Conversation KPI | Copy Transcripts (Child).
- Observe that the flow fails when formatDateTime() attempts to process 14/08/2026.
Expected behavior
The date selected/provided by the user should be normalized to an ISO 8601 compatible format before being processed by formatDateTime(), allowing Conversation KPI generation to work regardless of the user's regional date format.
Actual behavior
The child flow receives the regional date value (14/08/2026) and passes it to formatDateTime(), causing the flow to fail because the value is not in a supported ISO 8601 format.
Environment
No response
Additional context or logs
Description
The Conversation KPI "Generate KPI" functionality fails when processing dates in dd/MM/yyyy format.
When a date such as 14/08/2026 is provided, the Conversation KPI | Copy Transcripts (Child) flow fails while processing the date with the formatDateTime() function.
The flow returns the following error:
In function 'formatDateTime', the value provided for date time string '14/08/2026' was not valid. The datetime string must match ISO 8601 format.
This appears to be a date localization/formatting issue. The application provides the date using the regional dd/MM/yyyy format, while the child flow attempts to process that value directly as a datetime value.
The issue becomes especially noticeable from the 13th day of the month onward, because values such as 14/08/2026 cannot be interpreted as an alternative MM/dd/yyyy date.
Thank you for taking a look. Please let me know if any additional information or execution details would be helpful.
Steps to reproduce
Expected behavior
The date selected/provided by the user should be normalized to an ISO 8601 compatible format before being processed by formatDateTime(), allowing Conversation KPI generation to work regardless of the user's regional date format.
Actual behavior
The child flow receives the regional date value (14/08/2026) and passes it to formatDateTime(), causing the flow to fail because the value is not in a supported ISO 8601 format.
Environment
No response
Additional context or logs