You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@fineract.apache.org by "Ayush (Jira)" <ji...@apache.org> on 2026/10/21 15:06:00 UTC

[jira] [Commented] (FINERACT-2964) Send Asynchronous Events job is recorded as successful when events could not be sent

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

Ayush commented on FINERACT-2964:
---------------------------------

Hi! I’d be happy to work on this issue. Is anyone already working on it, or can I pick it up?

> Send Asynchronous Events job is recorded as successful when events could not be sent
> ------------------------------------------------------------------------------------
>
>                 Key: FINERACT-2964
>                 URL: https://issues.apache.org/jira/browse/FINERACT-2964
>             Project: Apache Fineract
>          Issue Type: Bug
>            Reporter: Jenny Liu
>            Priority: Major
>
> SendAsynchronousEventsTasklet catches every exception and returns FINISHED, so a run in which nothing could be sent (for example the broker is down) is recorded as a success in the job run history. The same happens when events were sent but could not be marked as sent. Monitoring that watches job runs cannot see either. The step and the job should fail with the error. The events stay TO_BE_SENT and are retried on the next run.



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