The custom NFL TD actions are triggering twice. Not sure if it triggers once for the score then again when the extra point gets kicked, but the action seems to be triggeing twice.
@ConnectedRoom I think what’s happening is that touchdown triggers are delayed, but extra points and field goals are happening in real time. At least this is how it seems to be on my system. If I set my delay settings to 0, there will still be a 20-30 second delay after a touchdown before lights, audio, and animations occur (this is fine with me, so it doesn’t spoil it). But with the same 0 delay setting, field goals and extra points are spoiled by 15-20 seconds. So the 2 triggers is really triggering once for a touchdown and again for extra points, it just seems like it’s a single for the touchdown. Hope that makes sense!
Guillaume
Team•
Dec 29, 2025
I am pushing a potential fix for tonight’s game. I will be monitoring the situation to see if it resolves the issue.
It has something to do with using 2 different data provider, one meant for speed of data, and one for depth of data.
There is a system remembering what already triggered, but both data providers don’t register the PAT the same way: one has the score with PAT applied to it (so 7-0), and one has the PAT separated from the initial touchdown (so 6-0 and then 7-0)
What happens, is that ConnectedRoom triggers 6-0 first and when the slower data provider triggers the 7-0, even though the mapping is completed, it gets perceived as a touchdown, instead of a PAT, which ConnectedRoom is not supposed to trigger anything for, except for 2pts conversions.
Robert
•
Dec 29, 2025
Thanks! That sounds like what’s happening.
Guillaume
Team•
Jan 6
Did the fix resolve the issue?
Robert
•
Jan 6
No double triggers over the weekend.
Robert
•
Dec 29, 2025
Happened a lot yesterday during the Bears v. 49ers game and last weekend during the Packers v. Bears.
Marc
•
Dec 14, 2025
Yes. Just occured at the Bill's game who have finally scored.
Guillaume
Team•
Dec 14, 2025
Is this issue is still ongoing? I can take a look into fixing this further more
Log in to comment and vote
Comments9
Robert
Dec 29, 2025
@ConnectedRoom I think what’s happening is that touchdown triggers are delayed, but extra points and field goals are happening in real time. At least this is how it seems to be on my system. If I set my delay settings to 0, there will still be a 20-30 second delay after a touchdown before lights, audio, and animations occur (this is fine with me, so it doesn’t spoil it). But with the same 0 delay setting, field goals and extra points are spoiled by 15-20 seconds. So the 2 triggers is really triggering once for a touchdown and again for extra points, it just seems like it’s a single for the touchdown. Hope that makes sense!
Guillaume
Dec 29, 2025
I am pushing a potential fix for tonight’s game. I will be monitoring the situation to see if it resolves the issue.
It has something to do with using 2 different data provider, one meant for speed of data, and one for depth of data.
There is a system remembering what already triggered, but both data providers don’t register the PAT the same way: one has the score with PAT applied to it (so 7-0), and one has the PAT separated from the initial touchdown (so 6-0 and then 7-0)
What happens, is that ConnectedRoom triggers 6-0 first and when the slower data provider triggers the 7-0, even though the mapping is completed, it gets perceived as a touchdown, instead of a PAT, which ConnectedRoom is not supposed to trigger anything for, except for 2pts conversions.
Robert
Dec 29, 2025
Thanks! That sounds like what’s happening.
Guillaume
Jan 6
Did the fix resolve the issue?
Robert
Jan 6
No double triggers over the weekend.
Robert
Dec 29, 2025
Happened a lot yesterday during the Bears v. 49ers game and last weekend during the Packers v. Bears.
Marc
Dec 14, 2025
Yes. Just occured at the Bill's game who have finally scored.
Guillaume
Dec 14, 2025
Is this issue is still ongoing? I can take a look into fixing this further more
Matt
Dec 14, 2025
It was as recently as last Sunday