Andy Cockerill
Andy Cockerill
Hi, we are facing the same issue reported here. I'm trying to understand how @jpalomaki has managed to work around it. Did you create an AMI with the github runner...
Thanks for the clarification. It is certainly a problem for us, one that we would like to see addressed.
We have also just seen this issue: ``` 2022-01-12T03:02:40.8630275Z Current runner version: '2.285.1' 2022-01-12T03:02:40.8636252Z Runner name: 'i-0f8710d183999929f' 2022-01-12T03:02:40.8637080Z Runner group name: 'Default' 2022-01-12T03:02:40.8638123Z Machine name: 'ip-blah' 2022-01-12T03:02:40.8641701Z ##[group]GITHUB_TOKEN Permissions 2022-01-12T03:02:40.8642978Z...
Thank you for the fast response. I followed your instructions and it discovered straight after a restart.
I'll leave it connected and get back to you when I have more info.
Further info: in the Logbook, at the same time as the error in the system log, I'm seeing: 
Thank you for the info, I'll try those.
I increased the scan level to 10 minutes (it was set to 1 as default) and selected "keep Bluetooth connections open". Errors have now stopped. I think it's probably worth...