Unable to activate global flow in workflow studio in yokohama release

[nobody-special]

I am getting an error when attempting to activate a global flow in workflow studio.  The error is:

Invalid values passed to the API, details: Table x_1843705_certif_0_st_XXX already has an active Flow associated to it. Deactivate the current Flow first.

I have removed all remote table definitions associated with this remote table but the error persists.  How can I determine the root cause of this message.  The flow in question was originally created as part of a scoped application and the flow is triggered from a remote table query.  After considerable effort I came to learn that scoped flows that have a remote table query trigger can't be executed from the global scope so I copied the flow to the global scope.  Since performing this action I'm not able to activate this global flow.

[Tanushree Maiti]

Hi @nobody-special 

1. refer KB : KB0745336 Flow Designer Activation & Testing Errors: "Invalid values passed to the API" 

Cause

These errors are usually caused by one of the following:

1. Mandatory fields in one or more actions are not populated
2. Multiple Trigger instances exist in the same Flow
3. Trigger configuration is incomplete or corrupted after recent changes

Resolution

Scenario 1: Mandatory Fields Not Populated

If the error states that a Record is mandatory and must be filled in, one or more actions in the Flow or Subflow are missing required inputs.

Steps to resolve:

1. If the Flow is not yet activated, attempt to activate it.
2. The activation error will indicate the action number where the issue occurs.
3. Open the Flow or Subflow in Flow Designer.
4. Review each action in the Flow.
5. Verify that all mandatory fields are populated.
6. Populate any missing required values.
7. Save and activate the Flow again.

Scenario 2: Multiple or Invalid Trigger Configuration

If the error indicates “Only one Trigger instance can be part of a flow”, the Flow contains more than one Trigger or an invalid Trigger setup.

Steps to resolve:

1. Open the Flow in Flow Designer.
2. Review the Trigger configuration.
3. Ensure the Flow has only one Trigger.
4. Make a small update to the existing Trigger (for example, reselect a field or condition).
5. Save the Flow.
6. Activate the Flow.

After updating the Trigger, the Flow should activate successfully.

2. Refer KB: KB2527100 Unable to Activate Flow when it has a subflow with input parameters starting with number 

[nobody-special]

Thank you for your reply.  I have carefully reviewed both KB articles but unfortunately they do not apply to this particular issue.