Plans table reaching row size limits
The _cbsubs_plans table contains 162 columns. Many are varchar(255) with some varchar(256) (is this a bug?) columns that could be converted to text type. Changing them to text type would result in a smaller 20 byte pointer to reduce row size and prevent hitting row size limit errors (8k byte default for innodb). Several yes/no (1/0) columns are also using tinyint(4) instead of just tinyint(1) wasting additional bytes.