feat(backend): low balance notiifcation

[ntindle]

For emailing, we want the user to know when an agent stopped because their balance was too low. This is the first step of that.

Changes 🏗️

• Raise InsufficientBalanceError from credit system rather than value error when user runs out of money
• Handle when an agent output isn't hooked up well
• Fix the contents of the email for low balance to be a bit more aligned with the PRD
• expose the topup intent from the db manager
• objectify the execution stats so we can pass it around a bit more type safe
• extract the notification stuff in manager into a function

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • Set balance to $0.01
  • Run an agent that costs something more than $0.01
  • Check you get an email
  • Check your top up link works

[deepsource-io]

Here's the code health analysis summary for commits 27a5635..1fe69ab. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗
Python	✅ Success	❗ 65 occurences introduced 🎯 60 occurences resolved	View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	1fe69ab
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/67c68b7ea0f793000895265f

[ntindle]

this will trigger multiple times

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	1fe69ab
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/67c68b7e08798f0008a75ef6

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 4 🔵🔵🔵🔵⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Error Handling The low balance error handling and notification logic could lead to race conditions or duplicate notifications if multiple nodes fail simultaneously due to insufficient balance. if isinstance(low_balance_error, InsufficientBalanceError): cls._handle_low_balance_notif( graph_exec.user_id, graph_exec.graph_id, exec_stats, low_balance_error, ) raise low_balance_error Null Safety The output value handling change could lead to unexpected behavior if the input_data dictionary doesn't contain the expected keys or contains null values. outputs[exec.input_data["name"]].append( exec.input_data.get("value", None) ) Resource Cleanup The running_executions dictionary items are only removed in the callback, which could lead to memory leaks if callbacks fail to execute. running_executions: dict[str, AsyncResult] = {} low_balance_error: Optional[InsufficientBalanceError] = None