Thanks Santosh,
It finally worked after applying the charge on the account which was showing invalid date manually till the current week. I think the users had entered the date manually instead of the date picker as you have stated. As Ippez suggested, if we can have the option to disable manual entry for date then I believe it will help avoid such issues. Regards; ******* Zayyad A. Said | Chairman & C.E.O Cell No.: +254 716 615274 | Skype: zsaid2011 Email: [email protected] Schedule Meetings: https://calendly.com/zayyadsaid Description: Email banner From: Ippez Robert [mailto:[email protected]] Sent: 02 May 2019 07:20 PM To: Dev; Santosh Math Cc: Mifos software development Subject: Re: Pay Due Savings Charges Job Failed If jobs are affected by manual date entries then in date fields we should have directives to disable manual entry of dates. I saw the same failure with some of our savings accounts also some time back but for me I was thinking maybe the date was not due. On Thu, May 2, 2019, 14:35 Santosh Math <[email protected]> wrote: Hi Zayyad, For savings accounts, TAC000017436 ,TAC000017224, check whether the dates are manually entered or date-picker is used. I think if date picker is used, it may not throw this error. On Wed, May 1, 2019 at 3:00 PM Zayyad A. Said <[email protected]> wrote: Hello Devs, Our client has a weekly fee charged on savings accounts, the charge has not been applied since 26th April 2019. When I check the cron job, I see it having an error pasted below: Error Log org.apache.fineract.infrastructure.jobs.exception.JobExecutionException: Apply Charges due for savings failed for account:TAC000017436 with message Failed data validation due to: invalid.date.Apply Charges due for savings failed for account:TAC000017224 with message Failed data validation due to: invalid.date. at org.apache.fineract.scheduledjobs.service.ScheduledJobRunnerServiceImpl.applyDueChargesForSavings(258) at sun.reflect.NativeMethodAccessorImpl.invoke0(-2) at sun.reflect.NativeMethodAccessorImpl.invoke(62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(43) at java.lang.reflect.Method.invoke(498) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(317) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(201) at com.sun.proxy.$Proxy241.applyDueChargesForSavings(-1) at sun.reflect.NativeMethodAccessorImpl.invoke0(-2) at sun.reflect.NativeMethodAccessorImpl.invoke(62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(43) at java.lang.reflect.Method.invoke(498) at org.springframework.util.MethodInvoker.invoke(269) at org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(322) at org.springframework.scheduling.quartz.QuartzJobBean.execute(112) at org.quartz.core.JobRunShell.run(213) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(557) Kindly advise what could have gone wrong? Prior to 26th, the charge was being applied without any issues. Environment: Ubuntu / Mifos X 17.07.01. Regards; ******* Zayyad A. Said | Chairman & C.E.O Cell No.: +254 716 615274 | Skype: zsaid2011 Email: [email protected] Schedule Meetings: https://calendly.com/zayyadsaid Description: Email banner -- Thanks & Regards Santosh Math QA Engineer <http://www.confluxtechnologies.com/> Conflux Technologies Pvt Ltd | Office: +91-080-41208662 | Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, Bengaluru, Karnataka, 560043 INDIA
