JasonZak The issue is occurring because the input date format does not match the format specified in the configuration.
In the Wrk Action configuration:
Current format: yyyy-MM-dd
Date provided: 2025/03/31
The format yyyy-MM-dd expects hyphens (-) between the date components, for example:
2025-03-31
However, the input date uses forward slashes (/), which corresponds to the format:
yyyy/MM/dd
Because of this mismatch, the Date and Time – Convert Format job is unable to parse the date and returns the error:
Unable to convert to provided date format (yyyy-MM-dd)
Resolution
Update the Current format field in the Wrk Action to: yyyy/MM/dd
OR
Ensure the input date is passed as: 2025-03-31
Note
The current configuration of the action is a bit confusing because it appears to be converting the date to the same format it expects as input. In its current state, the action does not seem to provide much value since no actual format transformation is occurring.
If the goal is to validate that the date matches a specific format, it may be more appropriate to use a regex based action such as "Compare content against regex pattern" instead.