PGRST201 on deleted foreign key

[rrcabrera9625]

I have a customer table with a foreign key pointing to the employee table. I recently added new fields also referencing employee, and after that, I started getting the following error:

    "code": "PGRST201",
    "details": [
        {
            "cardinality": "many-to-one",
            "embedding": "customer with employee",
            "relationship": "customer_created_by_fkey using customer(created_by) and employee(id)"
        },
        {
            "cardinality": "many-to-one",
            "embedding": "customer with employee",
            "relationship": "customer_deleted_by_fkey using customer(deleted_by) and employee(id)"
        },
        {
            "cardinality": "many-to-one",
            "embedding": "customer with employee",
            "relationship": "customer_updated_by_fkey using customer(updated_by) and employee(id)"
        },
        {
            "cardinality": "many-to-one",
            "embedding": "customer with employee",
            "relationship": "fk_assigned_seller using customer(assigned_seller_id) and employee(id)"
        }
    ],
    "hint": "Try changing 'employee' to one of the following: 'employee!customer_created_by_fkey', 'employee!customer_deleted_by_fkey', 'employee!customer_updated_by_fkey', 'employee!fk_assigned_seller'. Find the desired relationship in the 'details' key.",
    "message": "Could not embed because more than one relationship was found for 'customer' and 'employee'"
}

The problem is, I already removed the new field along with its foreign key and constraint. Still, I keep getting the same error.

As you can see, using the query below, it only returns one foreign key between customer and employee:

SELECT
  conname AS constraint_name,
  conrelid::regclass AS from_table,
  a.attname AS from_column,
  confrelid::regclass AS to_table,
  af.attname AS to_column
FROM
  pg_constraint c
JOIN
  pg_class cl ON cl.oid = c.conrelid
JOIN
  pg_attribute a ON a.attnum = ANY(c.conkey) AND a.attrelid = c.conrelid
JOIN
  pg_attribute af ON af.attnum = ANY(c.confkey) AND af.attrelid = c.confrelid
WHERE
  contype = 'f'
  AND conrelid::regclass::text = 'customer'
  AND confrelid::regclass::text = 'employee';

[
  {
    "constraint_name": "fk_assigned_seller",
    "from_table": "customer",
    "from_column": "assigned_seller_id",
    "to_table": "employee",
    "to_column": "id"
  }
]

I also tried running NOTIFY pgrst, 'reload schema'; — but nothing changed, the error persists.

Also tried project restart

Even tried database restore...

Why is this still happening?

[jeremykung]

I'm running into the exact same issue. I have reloaded the schema, verified the foreign key does not exist via SQL and through Supabase GUI, and it does not exist, yet the error persists. Very frustrating and no idea how to resolve the issue.

[rrcabrera9625]

Just to let you know… after a few hours the error in Supabase disappeared on my end. So it seems it might have been something related to caching. Could this be a bug in Supabase? Idk...

[jeremykung]

Strange, my issue still persists 14 hours after the fact

[GaryAustin1]

Sometime notify to reset the cache will not work. A Postgres (not REST) bug with notify.
A project restart (entire project and not just DB) should resolve if notify does not.

[GaryAustin1]

So you have any relations in the other tables between the same tables? Or is that what you deleted? Seems to be saying you have the relation you show AND a relation from courses to course_schedule and you need to use the examples they show to pick the one you want.

[jeremykung]

Updates & Information:

I've completely deleted the "course_session" and "course_schedule" tables from the database and for some reason the same PGRST201 error shows up with the two foreign keys in conflict after restarting the project. I thought deleting the tables could possibly reset the foreign keys but they seem to still persist even without the table?

I've also reset the tables and have attached screenshots of what the foreign keys exist for them. The error is referring to "course_session" and "course_schedule" but I've included the "course" table as well in case.

I don't see the fk_parent key anywhere

[GaryAustin1]

Check the API Gateway log to make sure these are going to the instance you think.

[jeremykung]

Here are the logs. They match my connect string instance:
zp...wkx

[GaryAustin1]

Looks like you are there. I'm out of ideas. Contact support if you have not already.
After all this time there should not be caching and the fk_parent is odd if you did not have a parent column or table. I don't find that as any sort of key for the current table or such in the PostgREST repository.