Multiple MID servers Flow Designer problem

[Emo Flore1]

Hi all,

I am working in an instance where there are multiple MID servers running, all seemingly working fine as they have the status "up".

Now what is happening and results in an error is that when using the standard Add User to Group action in Flow Designer, it chooses a different MID server every time, as designed. Yet, only 1 MID server works, as in the case of this MID server the Credentials get assigned and in the other cases the Credentials field is left blank. Does anyone know why this happens?

I have added screenshots to show what field I am referencing.

[Emo Flore1 · Accepted solution]

Hi,

Thanks for your reply! 

Revalidating a MID server is environment specific I guess. So, I will have to revalidate the MID server for my dev test and prod environment?

[Jon23]

Try validating the mid servers again. We've had similar issues with mid servers after patches have been applied.

You'll need to invalidate then validate.

-> To help others, please mark this as Correct or Helpful if this response has been of any use. <-

[Emo Flore1 · Accepted solution]

Hi,

Thanks for your reply! 

Revalidating a MID server is environment specific I guess. So, I will have to revalidate the MID server for my dev test and prod environment?

[Jon23 · Accepted solution]

You are correct, each environment will need their mid servers revalidated, assuming it fixes the issues in dev first 🙂

[Geoff_T]

A few things to check and be aware of. Check the credential record. It will look similar to below:

In your case the specific MID server that is working for you will most likely be specified. One option is to specifically apply the other MID Servers that could possibly be chosen. How do you know which others to specify; this is likely driven from the connection record setup. In the connection record below you see that MID Application is set to ALL. Click the preview record icon to see what MID Servers belong to that grouping. Those are all the MID Servers to apply to the credential record.

You could also update the Credential record so that it Applies to 'ALL MID servers'. This might also resolve your issue; but there are reasons for setting them up differently for certain scenarios.

Either way this should identify the root cause issue you are having.