How to ignore or getting rid of old migration

Hi. My current situation is:

• I created a migration for a table named "jobs" long ago before being aware of the table "jobs" for Laravel queues.
• I now need to implement queues with a database queue driver
• I do not use or need the old table "jobs"
• I have created and run a new migration to drop the jobs table
• I get [InvalidArgumentException] A CreateJobsTable migration already exists.when I try to run php artisan queue:table

Can I force the queue:table to ignore the previous table?

Or can I safely remove all tracks of the migration file even in production?

Or maybe I can make my own migration to create the required jobs table for queues?