STP failover disabled after outage

[complang]

Had an incident where a switch was supposed to fail over via STP. It did but fault-finder set the port to disable because of excessive broadcast.

M 03/04/16 12:36:35 02674 FFI: port 47-Administrator action required to re-enable.
M 03/04/16 12:36:35 02673 FFI: port 47-Port disabled by Fault-finder.
M 03/04/16 12:36:35 00332 FFI: port 47-Excessive Broadcasts. See help.

As I've understand it, fault-finder is ONLY enabled globally and can not be disabled on a specific port. If i set BC-limit to a specifik value on the interface, will this override the globally enabeled fault-finder broadcast-storm?

Don't want this to happen again. When STP fails over, there will clearly be more broadcast for a while.

[16again]

Why would  STP fail over result in additional broadcasts?  At proper fail-over , a loop should never be formed.

Better first make sure fail-over doesn't cause a loop somewhere.

[Vince-Whirlwind]

Start with all your STP config. How are the interfaces configured? 

Give us an idea of the topology and STP priorities on each switch in the network.

[complang]

On this particular switch (2530-48G) I have a primary LACP-interface/trunk, this with standard STP priority 4.
The failoverinterface on this switch is a standard copper with STP priority 5.

The core switch (5406zl) is STP root and was never down during this outage.

I've edited out the particular part from the network topology including this part (image).