Yeah that happens due to bitcoin blockchain reorganization (when Counterparty has to re-scan new blockchain blocks and during that time this error can appear if the rescan takes a a bit longer). The developers are working on devising a better way to scan new blocks but in the meantime a workaround is to retry a bit later like you did.