@dmvancura @ecayer

I believe we should be more explicit about our job statuses. Instead of only displaying "sent on," as we originally did, we could include more descriptive statuses such as "sent on," "scheduled for," or "sending." This approach would provide a clearer understanding of the job's progress. For instance, large jobs may take longer to process, making "sending" a more appropriate status to indicate ongoing processing.

What each state represents:

Scheduled for: Displays the time the user scheduled the job to send a future message.
Sending since: Indicates the time the job started processing.
Pending since: Displays the time the job was created if it has not started or finished processing.
Sent on: Shows the time the job was completed.

I really like this! It seems really helpful to add "Sending since". I'm still slightly hazy on why we might need to use the Created at status, though - this is for if a job was scheduled to start but it hasn't actually begun yet? Like the case where it's held up behind another large send?

i do like these statuses, but i'm also wondering about an "in queue" status, if that's ever necessary. it would be for jobs that are upcoming... thoughts?

so thinking out loud further on this, the above comment is a mute point, since we have "sending" and "pending"

@ecayer I see what you mean by the haziness of "created at", it doesn't quite convey that a message is in a "pending" state so @dmvancura and I decided to use "pending" if a message hasn't started processing or finished sending.