i am using RE-framework to automate emails but i dont want to use queue, is it possible
if yes, then how to make changes in reframework so that if there is an error it doesnt repeat from first transaction again also it should be able to handle duplicate
You can make use of DataRow instead of Queue
and if you don’t want it to repeat if an error occurs the Max Retry Number in Config file should be set to 0.
Hie @Vikram212 for working with mails in REFramework you need to change transactionitem variable data type from queue to Mail message. and also change datatype in process state .in init read email and store he output and pass the email output to transaction state so bot will take data one by one hope this link might help you.
queue will simply avoid duplicate but it wont help to take any action on duplicate
on top of that queue reference has only 129 characters limit but in my case i will be using email subject-sender name-sender email as reference which goes beyond 200 characters
I still reccomend using queues.
The 129 character limit is for the reference, but why store all that data in the reference.
When a mail is read you can get a unique message ID from the mail header, which would be ideal for a unique reference.
Data as subject, sender, name etc etc can easily be added as properties / specific content to the queue item for further sing them.
A couple of big advantages over queues vs non-queues:
you don’t need to track your progress
scalable, in case you ever need muliple performers over one dispatcher
reportable/ monitorable
auto retry options
controllable from orchestrator (start/stop/restart)
All out of the box. If you omit queues you’d have to implement these kind of features yourself more or less, which is a lot more work than changing a reference around.