Skip to content

fix: paginated calls of thousands of charges took to long #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sqhell merged 1 commit into from
May 6, 2026
Merged

fix: paginated calls of thousands of charges took to long #72

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions src/canton_mcp_server/server.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1413,18 +1413,17 @@ async def create_billing_credit(request: Request):
description=description or "Top-up via billing portal",
)

# Get updated balance
billing = await get_chain_balance(user_party)

logger.info(f"💳 CreditReceipt created: {contract_id} for {user_party} - {amount} CC")

# Intentionally NOT calling get_chain_balance() here. On a busy provider
# party (thousands of charges + credits) it adds ~25–30 round-trips of
# paginated /v2/updates walks (~30s) — long enough to exceed the
# autobot's 30s fetch timeout. Callers that need the post-credit
# balance should hit GET /billing/balance/{party_id} explicitly.
return JSONResponse(content={
"success": True,
"contractId": contract_id,
"amount": amount,
"balance": billing.balance,
"totalCredited": billing.total_credited,
"totalCharged": billing.total_charged,
})

except CantonBillingError as e:
Expand Down
Loading