TC team_control_point_round issues

Opened your VMF, looked around a little, and assumed the map's a traditional Hydro objective map minus the 2 bases.

Your TCPs have no I/O logic, meaning it pairs two opposing points and nothing else.
As your comment box says, you use OnStart/OnEnd outputs to control dynamic pathways.
Sounds complicated but like I told you last time, just do two territories at first to confirm they work.

It's obvious you just copy pasted the ABS TC prefab, which is dead-dry minimum for TC to function.
It doesn't have arrows, no team signs, no respawn filter doors, and so your map is missing what players expect like here:


Because each territory can be owned by either team, this spawn door won't open for BLU even if they own this point.
You should have a filter_activator_tfteam with an associated CP.
For example, "tc_filter_z" set to allow the owners of cp_z will allow the team owner Z to use those triggers and such.
It would be in your best interest to setup the things players expect as well.

Usually you want:
1) Pathways (where can we go)
2) Objective arrows (where do we go)
3) Team signs (who owns this point)

These are mostly controlled by your TCP rounds primarily in I/O.

Simply put:
OnStart is what you want to be shown for that round
OnEnd is what you revert from OnStart


This is my own example map, and here I use the A2C round to enable arrows and disable blocker walls
OnStart is what I want the map to change for this round.
OnEnd reverts my changes.




For arrows/team signs, there's an even easier solution:

When a round starts, and this CP is owned by Team1 (RED) I tell a relay to fire an output to fix team skins on all my signs for that territory




OnUser1 is for RED
OnUser2 is for BLU
It's like magic.

To summarize:
TCP I/O controls your map.
Start with 2 territories while building your logic.

This isn't everything, didn't talk about round timers or setup, it just covers your question on TCP rounds.

You know your map more than I do, I see no logic where I would expect.
Your rounds have different priorities too, which I'm assuming was intentional for some gameplay feature you had in mind, because it won't pick all of them random at once.
I mean this neutrally: I don't see I/O logic you're talking about in the map.

From a glance at your custom gamemode, it could be because priority 1 shares a CP with the priority 3 rounds (XY).
Usually we don't repeat CPs in a round until the game resets, so maybe that's the cause on top of your custom stuff.
Best of luck to you.