-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restrict cancelling of schedules of messages already sent #63
Comments
@lkwirica can you give more details about this issue? |
For integrity purposes, one can only cancel the record of a scheduled message BEFORE the message is sent out. Once the message has been sent, the record should not be deleted....This way, we can tell, all historical message schedules in the system |
@lkwirica This report only shows Active Schedules, Cancelling a schedule doesnt delete, it just deactivate. If you need a report of all scheduled messages we can then add a new report that list all scheduled messages (active and inactive), but not this one |
@lkwirica if you would like a new report please create a new issue that details what you want that report to include |
@ashaban 'Active Schedule' in this case means a schedule whose message has been sent out/ not sent? The schedules displayed are of messages already sent out....Shouldn't it then display schedules Not yet sent out? As in yet to be activated? |
Active Schedules is any schedule whose messages can still be sent out, remember that you can schedule a message to be sent out repeatedly i.e evey Monday and Tuesday, inactive schedule is the one that has either been cancelled or a schedule that can no longer be executed i.e you create a schedule to be executed twice in July, this schedule will be inactive in August. |
|
@lkwirica Yes, it should not, for now that feature is not supported, but you can still manually take them out by cancelling them. We will later add auto cancelling of schedules that has passed their time of execution, but this is not a priority for now since you can still manually cancel schedules. |
Related to issue #7
The text was updated successfully, but these errors were encountered: