PostgeSQL + Python 3.9 Query breaks if changed - why?

In my code, if I change this (working code - so the variables are working just fine)

cross_cross_OFR_SQL = '''
                    SELECT DISTINCT ON (racedate) * FROM testview
                    WHERE horsename = %s
                    AND racedate > %s
                    ORDER BY racedate ASC
                    LIMIT 2
'''
cur.execute(cross_cross_OFR_SQL, (cross_detailedhorse, past_racedate,))
cross_cross_OFR_SQLR = cur.fetchall()

to this

cross_cross_OFR_SQL = '''
                    SELECT DISTINCT ON (racedate) * FROM testview
                    WHERE track NOT LIKE '%KSA%'
                    AND horsename = %s
                    AND racedate > %s
                    ORDER BY racedate ASC
                    LIMIT 2
'''
cur.execute(cross_cross_OFR_SQL, (cross_detailedhorse, past_racedate,))
cross_cross_OFR_SQLR = cur.fetchall()

it breaks with this erro 'IndexError: tuple index out of range'

If I change it to

SELECT DISTINCT ON (racedate) * FROM testview
WHERE track NOT LIKE '%(KSA)%'
AND horsename = %s
AND racedate > %s
ORDER BY racedate ASC
LIMIT 2

it breaks with the error: 'TypeError: tuple indices must be integers or slices, not str'

I can not figure out why it breaks inside the python code.
Any ideas?

I want to exclude any tracks that have (KSA) in them.

It works fine in PGadmin4

As Tim Roberts and Adrian Klaver pointed out:

> The % character is special here, because it is a substitution marker (as in the %s you are using). To get a simple % character to pass through, you have to double it.