Hey @Vin5000!
I think it should be fixed when you connect the valid output pins of your variables to their respective target input pins.
(The valid ones would be the duplicate output pins that are not red. Don’t mind the red input pins tho (Target), they’ll turn blue again once they’re connected to the valid output pins.)
A similar thing happens when a custom event / function is deleted for example but their corresponding call nodes are still present. Or in case of variables, that might happen when a variable’s name is changed in the C++ code while it’s still referenced in the blueprint Event Graph. Sometimes even while migrating assets, updating the engine version, enabling / disabling plugins, or whatever happened in your case.
Hope this helps! 