Main view (Information Pop-up) - is broken at random

[jise]

The Main view is the informational page of the add-on where you can view the currently running Rules.
Running Rules information
Currently running rules are displayed in a tabular format. The Rule Name, Set interval, Last Run time and Total Run Count is displayed.

Hi, I don't know exactly when it started acting up, whether in the latest version of Chrome or before, but when I click on the extension icon, I don't always get the rules. sometimes it says there are no rules and I have to click on the icon again.

Otherwise, this is an amazing extension and thank you so much for it.

---

Session Alive 2.3
Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36

[arunelias]

Thank you for reporting this issue. I’ve encountered a similar problem myself and initially thought it was affecting only me. I’ll look into it and investigate further.

[jise]

Hi, I just want to let you know that this error no longer occurs for me. I don't know if the extension has been fixed or if the newer version of Chrome has stopped causing problems.

But at the same time, I would like to ask, as you can see even in my original screenshot, and I will attach the current screenshot here:

I have two websites on our intranet, and I run rules for them at the same time in the morning. Why does it become unsynchronized during the day, as if one rule were more tired? Yet both rules and intervals are the same, only the URL differs.

I should also describe my personal observations: sometimes it is synchronous even after half a day of operation after six or seven iterations, and sometimes it diverges in a few hours much more than in my screenshot. I have not figured out what triggers these two different scenarios.

---

Session Alive 2.4
Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36

[arunelias]

Hi, I’ve identified the issue and have corrected it in the latest version. Occasionally, Chrome suspends the extension, which can cause unexpected behavior. I’ve implemented an additional step to ensure the extension wakes properly from suspension. The rules running at different times might be related, as Chrome can also suspend inactive tabs. To help prevent this, you can add your sites to the “Always keep these sites active” list under Settings > Performance.

[jise]

I apologize in advance for hijacking the original thread with an additional question, but I'll continue anyway, because here is the previous image and text.

I have two websites on our intranet, and I run rules for them at the same time. Why does it become unsynchronized during the day, as if one rule were more tired? Yet both rules and intervals are the same, only the URL differs. I only changed the actual URLs for this source code listing:

{
"sa1743850872707": {
"bg_head_only": false,
"fg_interval": 22,
"fg_reload_sound": true,
"fg_trigger_uri": "https://a.intranet.company.country/qwe/rtyui/dashboard/DEFAULT/",
"loop_exit_200": true,
"loop_interval": "",
"loop_uri": "",
"notif_bgexit": true,
"notif_bgrequest": false,
"notif_fgexit": true,
"notif_fgreload": false,
"rule_disable": false,
"rule_name": "A",
"trigger_uri": ""
},
"sa1757166911529": {
"bg_head_only": false,
"fg_interval": 22,
"fg_reload_sound": true,
"fg_trigger_uri": "https://b.intranet.company.country/B",
"loop_exit_200": true,
"loop_interval": "",
"loop_uri": "",
"notif_bgexit": true,
"notif_bgrequest": false,
"notif_fgexit": true,
"notif_fgreload": false,
"rule_disable": false,
"rule_name": "B",
"trigger_uri": ""
}
}

As I have already described from my own experience, sometimes they run synchronously for many hours, but then suddenly, out of nowhere, they drift apart. I have not figured out what triggers these two different scenarios.

The rules running at different times might be related, as Chrome can also
suspend inactive tabs. To help prevent this, you can add your sites to the
“Always keep these sites active” list under Settings > Performance.

I checked this and both domains are listed in this section: Always keep these websites active - Websites you add will always remain active and will not be released from memory.

Please don't take this as a complaint. I am completely satisfied with the extension, I am just interested in why it behaves this way. Maybe it is some kind of error in how Chrome handles events for the extension, or maybe it is intentional to spread the load over time. No one else has described this here, so either it doesn't happen to anyone else, or no one else is concerned about it the way I am. 😇

I should also explain why I chose 22 minutes. On both sides, the login expires after 60 minutes, so I originally set it to 55 minutes, but sometimes it didn't work, so I set it to 45 minutes, then 33 minutes, and finally ended up with 22 minutes. I don't want to shorten the interval any further, but reliability is significantly higher with this setting. This way, the login only expires a few times a month (my computer is always on).

---

Session Alive 2.4
Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36