Detect not enough shards

This is follow up to Workflows completing early

Is it the expected behavior that when there are too few database shards configured that workflows will complete early without any indication to workflow or activity code that there is a problem?

If so is there a Temporal server log or some other metric that we can use to alert us of this problem?

Look a the “Choosing the Number of Shards” blog post.