[ 
https://issues.apache.org/jira/browse/FINERACT-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729687#comment-17729687
 ] 

Francis Guchie edited comment on FINERACT-894 at 6/6/23 11:16 AM:
------------------------------------------------------------------

[~vorburger] & [~bgowda] 
I have resurrected this issue as it is an issue that cron jobs for charges 
follow the *"ALL or Nothing"* approach. 
during a cron job execution, if one of the accounts being updated fails, the 
whole cron job is cancelled and an error message provide. 

We should find a solution to skip that one account and continue and keep a log 
of all failed accounts

[~ikimbrah] [~rrpawar] I know we have discussed this for a long time even in 
apache-fineract 1.7.3 it still exists. 
this relates to FINERACT-657  


was (Author: francisguchie):
[~vorburger] 
I have resurrected this issue as it is an issue that cron jobs for charges 
follow the *"ALL or Nothing"* approach. 
during a cron job execution, if one of the accounts being updated fails, the 
whole cron job is cancelled and an error message provide. 

We should find a solution to skip that one account and continue and keep a log 
of all failed accounts

[~ikimbrah] [~rrpawar] I know we have discussed this for a long time even in 
apache-fineract 1.7.3 it still exists. 
this relates to 
[FINERACT-657|https://issues.apache.org/jira/browse/FINERACT-657]  

> Scheduler Jobs Issue
> --------------------
>
>                 Key: FINERACT-894
>                 URL: https://issues.apache.org/jira/browse/FINERACT-894
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Job Scheduler
>    Affects Versions: 1.8.0, 1.8.1, 1.7.2, 1.8.2, 1.8.3, 1.8.4, 1.7.3
>            Reporter: Bharath Gowda
>            Assignee: Rahul Pawar
>            Priority: Critical
>         Attachments: Local Build Succes.png, Traivs Failure.png
>
>
> Following Scheduler Jobs are failing for the below mentioned scenario
> 1.Execute standing instruction Job
> 2.Pay Due Saving charge
>  
> Scenario:
> if there is a single savings account with insufficient balance, then Job is 
> failing and not processing its tasks for rest of the loans as well in the 
> system.
>  
> Expected behavior :Jobs should successfully execute it's task for all the 
> accounts and show the  error message of accounts for which there was 
> insufficient amount.
>  
> Steps to Reproduce
> :For "Pay Due Saving charge" Job
> 1.Create a Basic Savings account with deposit amount 1000 and add a monthly 
> charge of 5000.
> 2.Create second savings account with deposit amount 1000 and add a monthly 
> charge of 500.
>  
> then execute the "Pay Due Saving charge" Job, system should actually post the 
> charge for second saving account and through the error message for first 
> savings account. but system is not posting the charge for any of the loans.
>  
> :For "Execute standing instruction Job" Job
> 1.For client A - create a savings account with 100 balance, create a loan 
> with EMI of 1000 and add a standing instruction for the client to transfer 
> money from savings account to loan account on duedate.
>  
> 2.For client B - create a savings account with 1000 balance, create a loan 
> with EMI of 1000 and add a standing instruction for the client to transfer 
> money from savings account to loan account on duedate.
> then execute the "Execute standing instruction Job" Job, system should 
> actually post the transactions from savings to loan for client B and fail for 
> client A(due to insufficient fund) but as of the job is failing for both 
> clients.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to