When reviewing logs, an unparseable date error is sometimes observed
ERROR YYYY-MM-dd hh:mm:ss,zzz [-nnnnnnnnn | <automation_name> | <automation_run> | | {<group_name>}][(connectall-flows) thread #nnn - Split] com.go2group.connectall.model.transformer.ms.MSModelConverter: Conversion of datetime field failed due to the error: java.text.ParseException: Unparseable date: "YYYY-MM-ddThh:mm:ssZ"
The related date field is still updated in the Azure DevOps system.
ConnectALL 3.9.2 and lower
It is possible to define multiple date formats and the software tries each format to find a match with the presented date. If a match is not found, this error is generated.
While this is working as designed and can be ignored as long as the mapped date fields are being updated in Azure DevOps, the behavior has been changed in version 3.10 to not show an ERROR level entry.