You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove the requirement to match the exact second with 60-second differences from when a scheduled time is created.
馃帳 Pitch
Presently:
Using Appwrite Messaging, a user can set the time they want an SMS to be sent by date (MM/DD/YYYY) and time (HH:MM:SS)
Unless they match the exact second that they created the scheduled time with the time they wanted the SMS to be sent, they will receive an error message with suggested correct values.
Why this should be implemented:
It seems highly unlikely that users will ever set the correct time without checking a clock's time down to the second.
How it would be used:
Users can schedule their SMS more easily by removing the seconds and changing the step to 1 unit.
馃憖 Have you spent some time to check if this issue has been raised before?
馃敄 Enhancement description
Remove the requirement to match the exact second with 60-second differences from when a scheduled time is created.
馃帳 Pitch
Presently:
Why this should be implemented:
How it would be used:
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: