We have been experiencing increased error rate from our Twitter extractor recently.
Today we've updated the extractor and the issue seems to have been remedied. It is possible that some configurations will still finish with an error on import to Storage API. To fix that error, backup and delete the target table that failed to be imported. The results table creation has been improved in the extractor so that this error should not occur any longer, but it's possible some of existing tables have incorrect columns, or some of their existing columns will have to be processed again by the extractor upon receiving such data from Twitter.
We apologize for the inconvenience! Please contact us at firstname.lastname@example.org in case this error keeps occuring even after deleting problematic result tables.