@ajaya Ahead LSN usually happens when Postgres drops or advances the replication slot during an ungraceful crash or WAL segment recycling, while Airbyte state still points to an older committed position. If you can not rewind Postgres WAL, dropping the slot in Postgres and triggering a reset or full refresh on that stream from Airbyte is the only reliable fix.