I am involved in a task wherein as soon as User is created i will have to trigger a set of other processes which has to be taken care immediately as background process for which i am configuring in processes.yml . I tried the below code block where in i have configured supervisor(supervisor is working as expected for project as most tasks like mail , search indexes working) :YAML1234567triggers:post_user_updation:-event: updatequeued: truetime_shift: 10priority: 10
when i try the process with above code snippet to trigger it will not trigger anytime , but if i comment the queued: true part from above code it will trigger immediately & works fine.The only issue with this approach is UI is frozen until the trigger has to complete. I am not much aware on how priority No. is taken to consideration . Is that Higher Priority i.e like priority: 100 will be given more preferences compared to other? i have tried changing priority also to around 100 but it behaves the same way as not triggering at all. i have tried even with time_shift property as well which defines that the trigger should start within defined no. of seconds but i am not able to get it working. Link for Reference used to refer: orocrm processes documentation
I even tried with other way of using message queue but i found that there is no guarantee where in i found that a background job written under MQ will be triggered within a time span. Is there a option where in i can set in the given code reference (Message Queue Implementation Reference).
Is there a way where in i can implement time consuming code to be run in background but on event trigger immediately being picked & started without any other job queues dependencies for it to delay/not process at all?
Thanks & Regards,
You must be logged in to reply to this topic.