Runner: Cron triggered two times at once and missed one time

[Maxim-Mazurok]

Describe the bug
My action is scheduled to run every hour: https://github.com/Maxim-Mazurok/google-api-typings-generator/blob/master/.github/workflows/build.yml

But recently this action got run on the same hour twice and missed another run. You can see in the log below, that I expected job to run at 16:04:xx, but it got ran on 17:04:09

This is the start times of my action:
Mon, 09 Mar 2020 15:04:09 GMT (https://github.com/Maxim-Mazurok/google-api-typings-generator/runs/495421149)
Mon, 09 Mar 2020 17:04:09 GMT (https://github.com/Maxim-Mazurok/google-api-typings-generator/runs/495738420)
Mon, 09 Mar 2020 17:04:08 GMT (https://github.com/Maxim-Mazurok/google-api-typings-generator/runs/495738422)

To Reproduce
It seems like a one-off thing, I investigate every build fail and haven't found anything like this.

Expected behavior
It was expected for script to run every hour

Runner Version and Platform

2.165.2

Linux

What's not working?

 ! [remote rejected] types -> types (cannot lock ref 'refs/heads/types': is at 70187e254f5923245a73c42eefe7e5fa2637f4f1 but expected b990ce033f1106f6a9d5d76e7bb725b9490fc96a)
858
error: failed to push some refs to '[email protected]:Maxim-Mazurok/google-api-typings-generator.git'

caused by two runs at once

Job Log Output

Mon, 09 Mar 2020 15:04:09 GMT (https://github.com/Maxim-Mazurok/google-api-typings-generator/runs/495421149)
Mon, 09 Mar 2020 17:04:09 GMT (https://github.com/Maxim-Mazurok/google-api-typings-generator/runs/495738420)
Mon, 09 Mar 2020 17:04:08 GMT (https://github.com/Maxim-Mazurok/google-api-typings-generator/runs/495738422)

[TingluoHuang]

@andymckay do you mind take this cron trigger issue? 😄

[Maxim-Mazurok]

Off topic, but @TingluoHuang profile breaks GitHub 😅

[andymckay]

Thanks @Maxim-Mazurok @TingluoHuang, I've filed an issue internally with the team and we'll take a look at that.

[TingluoHuang]

close this as the internal issue has been closed.

[Maxim-Mazurok]

@TingluoHuang it would be great to know the outcome, since I haven't received any email from support regarding ticket closure.