@lawalong,

There are few points need you pay attention to:

1. On the repository’s Settings > Actions page, only the self-hosted runners installed in current repository are listed.

2. If you also have installed a repo-level self-hosted runner in your repository, and this runner has the same labels with the org-level runner. When you use the same labels to specify self-hosted runner in the workflow, the workflow will only use the repo-level self-hosted runner.
   For example:
   – the org-level self-hosted runner with the labels “self-hosted, Linux, X64”
   – the repo-level self-hosted runner with the same labels “self-hosted, Linux, X64”
   – the workflow in the repository

jobs:
  job1:
    runs-on: [self-hosted, Linux, X64]
    steps:
    . . .
  job2:
    runs-on: [self-hosted, Linux, X64]
    steps:
    . . .

job1 and job2 will only use the repo-level self-hosted runner.

3. You need to add some special labels to distinguish between repo-level and org-level self-hosted runners.
   For example:
   – the org-level self-hosted runner with the labels “self-hosted, Linux, X64, org-level”
   – the repo-level self-hosted runner with the labels “self-hosted, Linux, X64”
   – the workflow in the repository

jobs:
  job1:
    runs-on: [self-hosted, Linux, X64, org-level]
    steps:
    . . .
  job2:
    runs-on: [self-hosted, Linux, X64]
    steps:
    . . .

job1 will use the org-level self-hosted runner and job2 will use the repo-level self-hosted runner.

@brightran Thanks for your advise about label