Its a known issue, caused by a script update that changes the way the card determines when to apply its burn effect when a card is added both during or not during a chain. The new method was added to the card script before the new method was added to the game core, so the card is attempting to use a function the game core doesnt currently support. Once the game core is updated, this issue should be resolved.