Re: How is this possible "publication does not exist"

The problem is due to the reason that the slot used for sending changes to the subscription is created before publication. So, when we decode the changes (in your case 'insert') and check the respective publication, it won't exist by that time. The same problem is being discussed in a slightly different context in the email [1]. As a workaround, if you create a slot after creating a publication, you should not see this error.

[1] - https://www.postgresql.org/message-id/CAHut%2BPvMbCsL8PAz1Qc6LNoL0Ag0y3YJtPVJ8V0xVXJOPb%2B0xw%40mail.gmail.com