Why is my job cancelling when I have 'cancel-in-progress' set to false?

So I have 3 jobs in a workflow, 2 of which share the name concurrency ID

jobs:
############################### BOOT SIMULATORS #########################################
  node1:
    name: Selenium Grid Node 1
    runs-on: [appium-grid-hub]
    timeout-minutes: 250

  node2:
   name: Selenium Grid Node 2
   runs-on: [ios-appium-test-node]
   timeout-minutes: 250
   concurrency:
    group: ios-appium-test-runs
    cancel-in-progress: false


  test:
    needs: [node1, node2]
    #needs: [node1]
    name: Run tests
    runs-on: [appium-grid-hub]
    timeout-minutes: 270
    concurrency:
      group: ios-appium-test-runs
      cancel-in-progress: false

This workflow runs as devs create PRs, seems very frequently that if two jobs are waiting around, one of jobs in the ios-appium-test-runs groups ends up getting cancelled

I don't know how to prevent this, seems it won't cancel if it's in progress, but if a job is from another PR is "Waiting" then it will cancel another (these are PRs from two different branches BTW, I would expect a cancellation if someone pushes to the same branch causing a new run on their PR)

Start from the workflow's node2 and test jobs, focusing on their shared ios-appium-test-runs concurrency group and cancel-in-progress: false settings. Reproduce the behavior with jobs from two different pull requests, comparing queued, waiting, running, and cancelled states. Done means explaining the observed cancellation and identifying the configuration or documented behavior that prevents it.