Prisma Access Meraki Integration shows error "CustomException, error=System found to be in an inconsistent state, Halting Execution!"

• Prisma Access and Meraki SD-WAN is integrated successfully and onboarded few sites.
• Now, the onboarding is failing and the Strata Cloud manager shows following errors.

"CustomException, error=System found to be in an inconsistent state, Halting Execution!" 

• The Meraki side isn't receiving any API query from Prisma Access side. Another error message can be 

  Error in executing stage FetchGlobalData with exception handle_exception will be invoked System found to be in an inconsistent state, Halting Execution!
  Generic error 
  System found to be in an inconsistent state, Halting Execution!
   "msg": "Index on meraki is greater than the index in redis, meraki_index=28 redis_index=23

• Prisma Access(SASE)
• Remote Networks
• Meraki Integration

• This happens when the same API key (Meraki side) is being used on 2 Prisma Access tenants. 
• OR When using Non English Character in used Network names.

When using same API key in 2 Prisma Access tenants:
Although not recommended but if such a setup is used (Same API key used in 2 different Prisma Access tenants), Please ensure following to make sure there are on errors. 

1. One setup is in Paused State, While other is Enabled (Both can't be Enabled at same time)
2. Clear the Non Meraki VPN Peers from Meraki (if any ) manually before using on the Enabled setup

When the site discovery and integration stopped after using Non English character in network name.

1. From SCM (Strata Cloud Manager ) UI, disable the network (Toggle off ) on the site when non English character name.
2. Change to English name in Meraki Dashboard (Make sure the name does not cross 31 characters limit for the site name)
3. Clean up all the Non Meraki VPN peers on Meraki controller where local ID is greater then 23. (This is based on the error message where redis_index is equal to 23. If in another scenario, the value is x, Use that value).
4. Trigger an on demand discovery from the 3rd party site page (On top right). As a part of the discovery, the integration would recreate the peers that were deleted and things should go back to normal.

Support for non English character will be provided in future.