Sometimes idle

[Rickyc81]

Every now and then it happens that a started workflow doesn't start because on the host server I find the container started and the registered runner waiting for a job and on github I find the suspended job waiting for an available runner, does this happen to anyone?

thanks..

[smashedr]

In hindsight this may be related to my issue. I just setup a brand new runner, but it is always idle, it has never picked up a job, but has only been running for 24 hours.

My issue is token auth is not working, but app auth is. If you are having this issue, a workaround is to use app authentication. That is working flawless for me. Just can't get token auth to work.

#428

[myoung34]

Token auth works. Id ask the upstream project.

Proof that token auth works is here: #428 (comment)

[Rickyc81]

In hindsight this may be related to my issue. I just setup a brand new runner, but it is always idle, it has never picked up a job, but has only been running for 24 hours.

My issue is token auth is not working, but app auth is. If you are having this issue, a workaround is to use app authentication. That is working flawless for me. Just can't get token auth to work.

No no ... is not the same issue, my issue is different ..
my goal is to create a container from this image, after received a webhook with "queued" message and start it with repo_url etc etc .. and after receive "completed" i delete this container, so, sometimes this container is created succesfully, but it still remain in "listening" and the workflow on github remain in waiting for an available runner ...
this issue happens like once in 30 actions.. or similar.
my auth work perfectly ..

I currently have a fixed runner instanced and the problem has never occurred again, but it's strange...

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.