Hey team! Please add your planning poker estimate with Zenhub @ebma @gianfra-t @Sharqiewicz

@pendulum-chain/devs what are all the conditions when we show the traffic jam error to the users? Asking because marketing also wants to know the reasons when this error was shown, based on that will make changes if we need to consider more values here

It is based on many things actually, a maybe not exhaustive list is:

• Signer service is down (due to lack of funds, rate limit, etc)
• A failure to connect to the Pendulum nodes.
• (not yet implemented but planned) check for the oracle prices liveliness in Pendulum.

Let's not call the event parameter "digital traffic jam". How about we use 'initialization error' instead? Also, it might be better not to add this to the existing form_error event but create a new one. The initialization error will most or all of the time be unrelated to the form input so it makes sense to group it separately. For the parameters, I think we @pendulum-chain/devs should add all possible scenarios as a different parameter to the event so we can always be sure what the problem is. For example, for lack of tokens on the funding account, we should make clear in the event if it's a lack on the Stellar or Pendulum funding account, etc.

If I understand this correctly, then this new initialization_error kind will encompass any of these variations of errors that come from external problems.
Right now, we also have in insufficient_liquidity in form_error. I think this should on the initialization category also. But that depends on how the google analytics use that value already.

I think insuffiicient_liquidity can stay on the form_error as you will only face this error when you enter a specific amount into the form. So there has to be some form of interaction whereas for the initialization errors, there's not.