Details
There are various issues open about helping users understand why their runners aren't accepting jobs at the moment and allowing them to take action to fix it. This can occur at different points in the creation and management workflow (highlighted in yellow below).
![user-flow.png](data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==)
Use case 1: User leaves the workflow after landing on the registration page
✅ User chooses platform and fills out runner information.
🏃 User leaves once they get to the registration page (confirms they want to leave in the confirmation dialog), leaving the runner abandoned and never registering the runner using the authentication token.
➡ User returns to runners list, seeing the abandoned runner with no data attached to it. ⁉ User wonders what this means.
![runner-created-but-not-registered.png](data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==)
Use case 2: User leaves the workflow before connecting the runner after registering
✅ User chooses platform and fills out runner information.
✅ User registers the runner using the authentication token.
🏃 User leaves before running the runner (confirms they want to leave in the confirmation dialog), leaving the runner with a never contacted
status.
➡ User returns to runners list, seeing the never contacted
runner. ⁉ User wonders how to get the runner online and to accept jobs.
![tooltip.png](data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==)
Use case 3: User creates and registers runner, but the runner disconnects after some time
✅ User creates and registers the runner.
✅ Runner picks up jobs for some time.
➡ User returns to runners list one day, seeing that the runner now has a status of never contacted
. ⁉ User wonders how to get the runner online and to accept jobs.
![tooltip.png](data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==)