Trigger a flow from script - source record has changed

Hello SN developers,

We have a flow which is triggered by a script to wait for a end user answer.

If the same flow is triggered again for a RITM than it checks first: 'Is another flow already running?'.
If a flow can be found, than the first one will be cancelled and the second one will now wait for the end user feedback.

With the SN version 'Quebec' this works all fine.
The source record for the flow was always the RITM and so we were able to find already running flows and cancel them.

Now we habe the SN version 'San Diego' and the behavior has changed.
The source record for the triggered flow is e.g. the save-button-object. Or a client script. But not longer the RITM record.
The second flow is not able to find the other one and so both flows are running and they can affect each other.

For Incidents we can use the flow directly and do not need a trigger from script. The flow checks if an incident record fits the condition and then starts correctly. The source record is the INC record.

But for Requested Items there was no possibility to use the flow without a script trigger.

How can we deal with this issue?
Does anybody had such a request and was able to fix it?

At the moment I am thinking about reworking the flow to react directly on a task record update without the trigger from script. But that is quite complicate because some of the conditions are only available on the RITM record.

Thanks in advance!

Best wishes
Michaela