Abel Trejo Pineda

This workaround has worked like a charm for a while https://github.com/cypress-io/github-action/issues/518#issuecomment-1210979047 But now Test Replay is live and was disappointed to see this `Test Replay is not supported in custom...

This is the error I see now  The stdout ``` - Video - 6.96 MB /home/runner/work/.......mp4 - Screenshot - 109 kB /home/runner/work/......cy.ts/test name (failed).png - Test Replay - Nothing...

that was a new run from 30 minutes ago @rockhold

closing the loop on my previous [comment](https://github.com/cypress-io/github-action/issues/518#issuecomment-1697999194), Test Replay now works properly with the workaround [here](https://github.com/cypress-io/github-action/issues/518#issuecomment-1210979047), so still using that 👍

Don't know why i don't see it highlighted here, but this workaround has worked for me @nick-fields https://github.com/cypress-io/github-action/issues/518#issuecomment-1210979047

I believe I have a workaround for you guys @gagneet @bvanderneut , inside the `setupNodeEvents` I have this code ``` const envKey = config.env.envKey || 'default'; if (envKey !== 'default')...

@gagneet It seems you are not creating the `host` env variable inside `setupNodeEvents`, maybe rename the variable `envKey` to `host`? that was the name I used on my personal repo,...

I don´t think the `cypress.env.json` was ever meant to override the `config` object of `cypress.config.ts`, which is why I was proposing my workaround in [this comment](https://github.com/cypress-io/cypress/issues/22181#issuecomment-1232038319) Basically on `setupNodeEvents(on, config)`,...

@MikeMcC399 yeah we're already using that, but you can use tags only to filter slack notifications, I **want** these notifications, just in a slack thread instead

thank you very much @jennifer-shehane !