Customer has workers who might forget to clock out, hence, a batch job is created for clocking out any users who forgot or missed clocking out.

However, the batch gets executed and finished with no single record updated.

After debugging and testing multiple scenarios, it seems that the system if forcing the user to add a date format for the "profile date" parameter, and based on that parameter, all the records that match the specified date will be clocked out.

The main issue is that customer wants to run it for all the workers on daily basis which makes this an issue because it requires manual work or creating multiple batches with different dates.

If user tries to apply a workaround by adding date(0) in the inquiry from UI, error message gets triggered retesting that the profile date is specified in date format.

We also found a community support post which was raised before for the same behavior and we are raising this idea to consider design change of this functionality.

Ref: Automatic clock out workers - Batch job AX2012

Otherwise, user has to clock out each worker manually or the production orders can't be ended/RAF since the job is not finalized unless the worker clock out.