i found the issue , its because i dropped the jobs table from the database but when a new one created why its still complaining about a duplicate like for the error to go away i had to exceed the jobs numbers i had earlier like running the script 12 times since i had 11 records.
where is this settings managed ?
You probably need to drop the pipeline and job output tables as well. They are stored as LiteDB files that match the job ids. We dont manage this IDs directly.