Random 404s on the github action

[zac-hsone]

As seen in the screenshot we randomly get 404s from time-to-time and we're not sure why? I've had to just say continue if fail on the job because it will trigger a build to fail because of it. Anything we can do?

[twk3]

@zac-hsone you can get a 404 if the command doesn't find the previous run. (note that it only looks at completed runs, so if you retry before the run is complete it won't find it).

That being said, I would double check your ci-build-id. It looks like this action is using the default, but if you are using a different syntax for our reporter, you need to update the action to match.

The default setting for the action is:

previous-ci-build-id: ${{ github.repository }}-${{ github.run_id }}-%<= ${{ github.run_attempt }} - 1 %> so you may need to adjust it if you've customized the build id anywhere in your config.

So if you job changes the build id at any point for our reporter, you need to also make a similar adjustment to the action settings. (Just be sure to still minus 1 from the run_attempt for the action)