Open for Voting
UX Bug: Misleading Queue Failed Notification
Problem:
When "all items in queue finish encoding" notifications are turned on, but a previously failed or cancelled render exists in the queue, the resulting notification reads: "Queue Failed - Queue stopped before finishing all items." This leads a user to believe that one of their intended render items failed, rather than one of the items that was failed/cancelled when the queue was started. We can assume that the user already knows (or doesn't care) about such failed/cancelled items and doesn't need to be notified of them.
Ideal fix:
Include more descriptive data in queue finished notifications, like number of successful/failed items eg. "Queue Failed - 5 items done / 1 item failed" Bonus: Maybe even total render time could be included!
Simple fix:
Keep the current notifications but only evaluate the status of items where the status was "ready" when the queue was started. If one of those items fails, send the Queue Failed notification.
Current Workaround:
Delete any failed/cancelled render items before starting the queue.
When "all items in queue finish encoding" notifications are turned on, but a previously failed or cancelled render exists in the queue, the resulting notification reads: "Queue Failed - Queue stopped before finishing all items." This leads a user to believe that one of their intended render items failed, rather than one of the items that was failed/cancelled when the queue was started. We can assume that the user already knows (or doesn't care) about such failed/cancelled items and doesn't need to be notified of them.
Ideal fix:
Include more descriptive data in queue finished notifications, like number of successful/failed items eg. "Queue Failed - 5 items done / 1 item failed" Bonus: Maybe even total render time could be included!
Simple fix:
Keep the current notifications but only evaluate the status of items where the status was "ready" when the queue was started. If one of those items fails, send the Queue Failed notification.
Current Workaround:
Delete any failed/cancelled render items before starting the queue.
AdChoices