X_SCRAPE_EGRESS_IN_PAYLOAD
Means
the run exit carries a credential that is also in the job payload
Typical cause
scrape({ egress }) answered a proxy URL whose password is readable out of the run's own input, so it rode the queue payload and is stored in x_jobs in the clear. Refused before the browser opens; terminal, because every remaining attempt reads the same row
Fix
look the exit up by id inside the worker — egress: async ({ connectionId }) => (await repo.connectionById(connectionId))?.exit — and drop the exit field from the scrape input