Open VoxBorealis opened 1 year ago
There is a bug in the scheduleMessage function. Currently it only saves the job to the database when it has already found any job on the given channel -- this means that newly created jobs are never saved to the database unless you perform the /tilaa
command twice.
TODO:
startScheduling
function, which would mean that we fetch the jobs from the DB and then save them immediately after... It appears that even though the job is saved to the DB, it will not persist through restarts(?)
For some reason the app is not updating/editing the scheduled messages in the Tampere channel in production. Locally everything works as intended.