The debugging procedure in this case is as follows:

1. Determine the list of participating beta operators (or a list of all beta operators if you don't have access to client logs)
2. Note the DKG start timestamp, let's call it DKG_start (can be taken from the requestNewWallet ETH transaction)
3. Use https://status.threshold.network/ and check if all participating operators where up in the time range between DKG_start and DKG_start + 8h
4. If an operator was down at least for a while, they are most likely the culprit. The operator should double-check their node. If all operators were up, this may indicate that some operators are too slow and they not acted on time during the DKG ceremony. In this case, all operators should ensure they meet the system requirements for beta operators.
5. Cancel the process by calling notifyDkgTimeout on the WalletRegistry
6. Start new DKG by calling requestNewWallet on the Bridge (parameters are tricky here but I will try to expose a cloud function that will help with that soon)