Thank you for the clarification
However i feel i must challenge you on this.
Deadline and postpone does NOT have the same behaviour.
Postpone gives a bottom limit that ensures the queue item WILL NOT be processed before the date sat.
If you translate this behaviour to deadline, it would mean that deadline should set an upper limit that ensures the queue item WOULD NOT be processed if date was reached.
I also feel that the name “Deadline” is misguiding for the same reason. As you can read from above posts, when i hear the word Deadline, i would assume that the item is “dead” (abandoned) after reaching the “deadline”.
a wording like "Prioritize if after " would be much easier to understand. Even your old wording “Due date” would be better i think.
As you say, UiPath have the behaviour documented, so it clearly is working as intended.
Would you consider implementing an “abandon date” for queue items?
The usecase i have right now:
I have a robot that runs once a day that processes queue items.
If the processes fail with business exception, i want to try again tomorrow.
If it fails tomorrow i want to abandon it from the queue.
If it fails with application exception, it will auto-retry.
If the auto-retry fails, i want to abandon it from the queue.
This means i cannot use queueitem.retryNo, as if it fails once with application exception and then on the auto re-try fails with application exception, retryNo will be 2 where it should be 1 application and 1 business.
I also found no way of getting the creation date of a queue item, so i can’t make my own logic, unless i “manually” stamp queueitems with date when they are crated
To sum up:
It’s not impossible to workaround this, but since UiPath already made our life easier with postpone, “deadline” and priority, why not also make one for abandon date?