ATLAS
- signed_url issue still a problem (Seee last week notes)
  - more monitoring fields to understand the issue
- Alma9 testing
  - Servers worked well
  - Reaper issue with gfal2
    - CPU Consumption very high
    - Worked correctly, but much slower
    - Did not investigate further (yet)
    - Standard RPM was used
    - Needs investigation by GFAL team
CMS
- Lag between FTS and Rucio
  - Transfer Success / Failure until it shows up in Rucio
    - 8h gap, 24h gap, ... seen
    - Is conveyor-receiver ran?
      - Radu: Yes, but not in the full_update mode, so it will still wait for finisher #5532
    - Need to understand if it is held by finisher or by poller/receiver
  - Recovery from accidental mark as lost issue
    - finisher took a morning to work through 1M requests
    - CMS running 4 x 5 = 20
    - ATLAS runs 42 finisher threads (=6 x 7 or so)
- Lag in staging from tape
  - Probably not a Rucio thing?
    - FTS issue?
Fermilab / DUNE / RUBIN / ...
- DUNE
  - Protocol priorities
    - delete-protocol reshuffles existing protocol priorities - no like :-)
  - Issue with renewing tokens not working
    - Fixed in next weeks LTS release
  - rucio upload failing to dpm sites without full parent directory tree
    - gfal does not trigger parent directory creation?
    - Noticed in move from 1.26 to 1.29
- RUBIN
  - data ingest test successful
ESCAPE / InterTwin
- Not much news
MultiVO / RAL