SMS messages are sent before actual transactions are completed.

Open
  • Is something wrong?
#9 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
backend

Research direction

Start by reproducing the reported savings-account withdrawal flow: create an SMS campaign, withdraw more than the available balance, and observe the message before the insufficient-balance error. Trace the withdrawal and SMS-trigger paths to determine their ordering; done means successful transactions trigger messages, while rejected withdrawals do not.

Written by the indexing model from the issue text.

Description

@nazeer1100126 , Could you please have a look at this issue.

Steps to reproduce this
Create an sms campaign for savings account withdrawal
Make a withdrawal from an account and put the amount more than the actual available balance.
Message will be sent { that you have withdrawn the amount and balance is so much} - this message body depends on what you have actually put as you message body
Fineract will throw an error - Insufficient Balance.

So to me Fineract should first have successfully transactions before any sms campaign is triggered for sending.

Dominant language
Java
Stars
28
Forks
84
Avg merge
6m
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openMF/message-gateway

All issues in openMF/message-gateway

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.