[BUG] Multi-Project Platform - Major UI / Navigation issue. Shows incorrect Project / switches project / can't run jobs.

[Arthidon]

Mage version

9.70

Describe the bug

Video Link Replicating Issue: https://1drv.ms/v/s!AlYu3S2PXVu9mcximMZPCamEj6LVfw?e=FqHfvG

• The project it shows you are in and the content displayed on the page sometimes is mismatched.
• This can happen in any menu / logs / pipelines / edit pipeline
• Somtimes it will show you the correct project and content but running pipelines will not work or UI will not work
• Sometimes you will get errors telling you the block file doesn't exist (because it is looking in the wrong path)
• PIpeline logs not showing because I do not think the pipeline is actually running due to this issue
• not sure if "When running a block while editing a pipeline, output the block messages to the logs" is working or not... can't get pipeline to run without a trigger
• When trying to run pipelines with triggers, they say they are successful but we are not seeing results at destination even though trigger states it was run succesfully.
• 5/7/2024 - rollbacked to Version 9.68 - above issues seem to be less frequent. Developers can now sometimes run blocks in edit mode. However, I am not sure if the rollback helped here or if the redeploy is what helped.
  After the rollback to 9.68 Devs are still having problem with runnign blocks in edit pipeline Mode

To reproduce

see video above:

• navigate to different pipeline menus
• try and run blocks in edit pipeline

Expected behavior

No response

Screenshots

This is example of being in the correct project and the block not running / getting stuck

Operating system

No response

Additional context

No response

[johnson-mage]

@Arthidon Got it, we do plan to make some changes to the multi project platform so it can run smoother. But thank you for the detailed PR so we can keep track.

[wangxiaoyou1993]

@Arthidon do you have multiple users using different subproject in the same instance?

[Arthidon]

Yes, i may be working in project > X and someone else may be logged in working in project Y. We understand that we both cannot be working in the same project without stepping on each other. So 1 dev per project atm is what we are doing.

Currently we have 4 teams testing in the mage instance.

projects:
project1:
path: TeamsRootFolder/SpecificTeamFolder/ProjectFolder
project2:
path: TeamsRootFolder/SpecificTeamFolder/ProjectFolder
project3:
path: TeamsRootFolder/SpecificTeamFolder/ProjectFolder
project4:
path: TeamsRootFolder/SpecificTeamFolder/ProjectFolder

[wangxiaoyou1993]

Got it. Then we've merged the PR to support the active project per user.
#4865
That'll be released in version 0.9.71.

[Arthidon]

Do you think this issue was also causing the issue stated in #5049?