Hi Bhaskar, Thank you for reaching out.
I’d appreciate it if you could clarify a few points to help me better understand the issue: What exactly do you mean by “custom scheduler”? How are the schedulers deployed across multiple servers? Are they part of the same application instance or running independently? A bit more detail on your setup and the logic you’ve implemented would be helpful in identifying the root cause and suggesting a solution. Regards, Adam > On 2025. Jun 30., at 10:11, Bhaskar Tiwari <[email protected]> wrote: > > Hi Team, > > I’ve implemented some custom schedulers in Fineract using existing patterns. > However, I’m encountering an issue with duplicate entries when two servers > are running concurrently and share the same database. > While I’ve added logic to prevent duplicate accrual entries when schedulers > are triggered multiple times, the problem arises because these schedulers are > running on separate servers. As a result, each instance bypasses the > duplication check, leading to duplicate accrual entries in the database. > Is there a recommended way to manage custom schedulers in a multi-server > setup to avoid this issue? > > Looking forward to your suggestions. > > Regards > Bhaskar Tiwari > > "Print this mail only if absolutely necessary. Save Paper. Save Trees." > Disclaimer: “This electronic mail message sent from StrideOne (Stride Fintree > Private Limited) may contain Confidential/Restricted/Internal information and > should only be viewed by the intended recipients. Under no circumstances may > any such information be disclosed, copied, used or distributed to any > unauthorized persons or entities without the written consent of Strideone. If > you are not the intended recipient, any review, retransmission, dissemination > or reliance on the content of these materials is strictly prohibited and may > be the subject of legal action. If you received this email in error, please > notify the sender and delete the message immediately.” >
