getTransactions/getBalances classified 401/400/422/ASPSP errors but let any
other RequestException fall through to a raw re-throw, so an upstream 500
('Internal server error') from EnableBanking or the ASPSP propagated and was
report()ed as an app error (Sentry PHP-LARAVEL-3J: 36 events / 3 users).
A 5xx is a transient server-side failure — the same class as a
ConnectionException, which is already wrapped as TransientBankingProviderException
(logged at warning, retried, self-healing). Classify any upstream 5xx the same
way in both getTransactions and getBalances via a new isTransientServerError()
helper, so provider outages retry/self-heal instead of paging Sentry.
Non-5xx paths (401/400/422/ASPSP + genuine 4xx client errors) are unchanged and
stay reportable.
|
||
|---|---|---|
| .. | ||
| .pest | ||
| Browser | ||
| Feature | ||
| Fixtures | ||
| Performance | ||
| Support | ||
| Unit | ||
| Pest.php | ||
| TestCase.php | ||
| bootstrap.php | ||