Hi Colin,
I, indeed, missed this important column.
tags
column value is test
.
It looks like the rule didn’t have any tag at first. Then, the test
tag was manually added to ti. And later on, a new version of our plugin globally added the test
tag to this rule. This “duplication” might be the root cause of the migration issue.
Also, for another instance on which the rule was not manually tagged as test
, the database migration worked well.
Should I manually update the database to empty the tags
column for this rule? Or do you plan to provide a fix to support this corner case?
Many thanks!
Regards
Nicolas