How to troubleshoot errors related to changing alternate keys in Network?
When wanting to update alternate keys that may have been improperly assigned, customers use the following advanced source subscription feature:
The most common error related to Alternate keys is :An attempt is being made to update an already existing alternate key from <x> to <y>.
The corresponding backend error is thrown in the Mule Log: skip None-ACT cluster in Activity <MM_7267wgwec8yn> when override Alternate Key[Ignoring]
There are two reasons for this error:
- The above mentioned advanced feature is set to true and the subscription is initially loading data with new alternate keys.
- The above mentioned advanced feature is either set to false or not included in the advanced features of the subscription.
Network Help Documentation: N/A
Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.