bcgov / bcgov/lcfs

LCFS - Bug: Transfer Recorded by Director Shows Pending for Buyer and No Balance Change (Prod)

Open
#3,191 0 comments 0 reactions 0 assignees View on GitHub
bug Credit Transfers & Transactions High
Dominant language
Python
Stars
6
Forks
6
Avg merge
2d 4h
Merged PRs (30d)
87

Description

**Describe the Bug**
A transfer recorded by the Director was processed as an adjustment in the database. The seller’s balance was reduced accordingly, but the buyer’s balance did not reflect the corresponding increase. The buyer reports that the transfer still appears with a "pending" status in their view, suggesting it may not have been fully processed or confirmed on their end.

**Expected Behaviour**
Once a transfer is recorded and processed, both the seller’s and buyer’s balances should update accordingly. The buyer should see the transfer as completed, not pending.

**Actual Behaviour**
- Seller’s balance is reduced.
- Buyer’s balance remains unchanged.
- Buyer sees the transfer as "pending" in their interface.

**Implications**
This could result in inaccurate credit balances, confusion for the buyer, and potential compliance or reporting issues. It may also indicate a breakdown in synchronization between the adjustment logic and the user-facing status indicators.

**Steps To Reproduce**
Steps to reproduce the behaviour:
User/Role: IDIR/buyer BCeID
1. Director records a transfer.
2. Transfer is processed as an adjustment in the database.
3. Buyer logs in and views their credit balance.
4. Buyer sees no change in balance and transfer marked as "pending".

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by tracing the director-recorded transfer and its adjustment path, then follow how the buyer balance and transfer status are exposed. Done means the buyer balance increases and the transfer appears completed rather than pending, while the seller reduction remains correct.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.