https://gitlab.synchro.net/main/sbbs/-/issues/990#note_7740

Did you recently change it to Disabled maybe and the SBBS event thread didn't recycle the configuration?

There's certainly code (in main.cpp) to skip timed events that are disabled:

```
/* Timed Events */
for (i = 0; i < sbbs->cfg.total_events && !sbbs->terminated; i++) {
if (sbbs->cfg.event[i]->node > sbbs->cfg.sys_nodes)
continue; // ignore events for invalid nodes

if (sbbs->cfg.event[i]->misc & EVENT_DISABLED)
continue;
```

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/issues/990#note_7748

Ah I was probably hogging node 1 after the config change. Could that have caused my issue?

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/issues/990#note_7749

Yes, the event thread runs in the terminal server, so any changes to event configuration (e.g. in SCFG->External Programs->Timed Events) requires a successful recycle of the terminal server for the event thread to "see" those changes.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

close https://gitlab.synchro.net/main/sbbs/-/issues/990

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/issues/990#note_7752

Ah in which case, I'll close this issue.

Thanks for the support.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net