Kaleo workflow fails on additional portal instances when manual database shard is enabled if liferay is built from the trunk. It only behaves normal on the default instant. Hope the bug will be fixed before the 6.1.x release!

I have built sharded Liferay's with manual allocation just recently. It appears that the Kaleo system only stores data in the default data source, instead of splitting it across shards. Despite this the kaleo tables are built into every shard, they just remain empty.