ksh - issue with (non-existing) jobs

I just noticed in a ksh window that 'jobs' indicates two active jobs.

[2] +  Running                 a_command $( find -type f ... )
[1] -  Running                 a_command $( find -type f ... )

$ kill %1 %2
kill: %1: no such job
kill: %2: no such job

$ pkill a_command          # doesn't change the status.

New jobs consequently get job numbers starting with %3.

Somehow the ksh instance seems to have missed the job termination,
and the job management tables seem to have got corrupted.

Any idea what's going on and how to get rid of those undead jobs?

I'm running Version AJM 93u+m/1.0.8 2024-01-01

Janis