Workaround for "Wrong Response Id" Error

In the specific situations mentioned below, we have experienced situations where the dApp reported a transaction as failing with the error code "wrong_response_id". This error is caused by a transaction processing failure which resulted in the operation being reverted (i.e. canceled). This cancellation was not adequately interpreted by the MetaMask browser extension and thus not correctly reported to the dApp.

Encountering this error does not result in the loss of gas or POLY, as the transaction is reverted. Should the approval of the POLY transfer succeed and the operation immediately following fail, restarting the operation will not result in a loss of POLY as the application will detect that the POLY transfer was already approved and it will automatically proceed to the following step.

Situations in which the error above was experienced either once or in sequence:

• Reserving a ticker. This operation may fail due to the token name already being reserved. We recommend waiting a few more seconds, then restarting the operation. If the operation fails again, we recommend changing the token name. 
• Creating a security token. If the dApp did not move ahead after having the token created, you may be able to mistakenly attempt to "create" the same token again, resulting in this error. Refreshing the page should show that the token was already created and allow you to proceed to the next step.
• Minting. The whitelist operation may succeed but the minting may fail. This can be due to a variety of reasons, namely that the transfers are paused or that the limit of investors has been reached. Changing the minting list, exporting the current one, and observing whether any of these limits has been reached will help understand the origin of the issue and resolve it.
• Creating an STO. Some invalid values may cause the STO creation to be rejected. Typical invalid values include invalid token amounts (e.g. starting with 0) or currencies not being divisible (e.g. USD). Fixing these amounts should solve the problem.

Our Team is actively working on improving the error handling and expect these errors to be reported accordingly in subsequent releases.