Scheduling a post
For creators posting later — how to schedule, why “Save draft” loses the time, and what “Did not go out” means.
Turn on Schedule it, set Date and Time, and press the primary button — which now reads Schedule for and the time you chose. The post appears in Queue until it goes out.
With the switch off, the row reads “Off — this publishes the moment you press the button.” With it on: “Goes out automatically. It will appear in Queue.”
Save draft does not keep the time. The app says so at both places you can act:
Saving a draft does not keep this time. The post stays a draft and will not go out on its own — schedule it to keep the time.
Save draft saves the post and its files and stops there. The time you picked is not stored, the post does not enter the Queue, and it will never publish by itself.
If you want the time kept, press the Schedule for … button, not Save draft.
The rules for a time
- It must be in the future. A past time dims the button with “That time has already passed.”; the server’s own version is “scheduledAt must be in the future”.
- It must be within 365 days. Further out is refused with “scheduledAt must be within 365 days”.
- Both Date and Time are needed. One without the other gives “Choose a date and a time.”
The time is sent with your time zone attached, so it fires at the moment you meant regardless of where EVVA’s servers are.
A scheduled post stays a Draft with a time on it — scheduling is not a separate status. It publishes itself when the time comes.
What happens at the time
EVVA publishes the post, and re-checks the whole queue every five minutes so a missed job is picked up rather than lost. A publish that hits a temporary problem is retried up to five times, thirty seconds apart.
The same checks as a manual publish apply at that moment, including media readiness.
”Did not go out”
If a file on the post is not serveable when the post comes due, EVVA keeps trying for one hour. After that it gives up, records why, and the Queue row reads Did not go out.
The post is not published and not lost. To recover it:
Changing or cancelling a schedule
Rescheduling replaces whatever was set before. You do not need to cancel first.
Cancel schedule stops a post from going out. It is safe to press twice — cancelling something that is no longer scheduled is not an error. If the cancel itself fails you are told: “That schedule could not be cancelled just now.” The post is still scheduled in that case; try again.
Cancelling a schedule is never taken away from you. It works even while a creator account is suspended — so a post that is about to publish can always be stopped.
Only a draft can be scheduled. An already-published post is refused with “Cannot schedule an item that is already published”.
If the Queue says “Could not read your queue” or “Your queue could not be read just now.”, that is a failed read — not an empty queue. It deliberately does not say “Nothing is waiting”, because that would invite you to reschedule a post that is already scheduled. Reload before you act on it.