Banchii · Log
1 log error(s) detected
Error
### Error 1: CN reversal posting failed * **Root Cause:** The application attempted to post a financial transaction to reverse a credit note (`CN`), but all the line items in the transaction had a value of zero. Accounting systems typically reject such transactions as they have no financial effect and are considered invalid. * **What Went Wrong (in simple terms):** The system tried to make an accounting entry to cancel a credit note, but the entry amounte…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-11 07:48:04 UTC
View full analysis
### Error 1: CN reversal posting failed
* **Root Cause:** The application attempted to post a financial transaction to reverse a credit note (`CN`), but all the line items in the transaction had a value of zero. Accounting systems typically reject such transactions as they have no financial effect and are considered invalid.
* **What Went Wrong (in simple terms):** The system tried to make an accounting entry to cancel a credit note, but the entry amounted to $0.00. The accounting system correctly refused to record a transaction that does nothing. This likely happened because the original credit note was for a zero amount, or a bug in the calculation logic produced a zero result.
* **How to Fix:**
* Investigate the credit note that the system was trying to reverse. Confirm if its total value was zero.
* Review the code that generates reversal postings. It should either prevent attempts to post zero-value transactions or handle zero-value credit notes gracefully (e.g., by marking them as reversed without creating an empty accounting entry).
* Consider adding a validation rule to prevent the creation of zero-value credit notes if they are not a valid business use case.
* **Severity:** **HIGH**. This indicates a failure in a core financial process (accounting postings). While it doesn't crash the application, it can lead to inconsistent or incorrect financial records, which is a serious business logic issue.
View raw incident details
Fingerprint: 531ffa396757
Occurrences: 1
2026-09-11T07:47:13.765486987Z [invoices] CN reversal posting failed: Error: Posting has no non-zero lines
Banchii · Log
1 log error(s) detected
Error
### Error 1: Credit Note Reversal Failed * **Root Cause:** The application tried to commit a financial transaction (a "Credit Note reversal") where every line item had a value of zero. Accounting systems are designed to reject such transactions as they have no financial impact and are considered invalid. * **What Went Wrong (Simple Terms):** The system tried to make an accounting entry, but the amount for the entry was $0.00. The accounting module correct…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-11 07:29:52 UTC
View full analysis
### Error 1: Credit Note Reversal Failed
* **Root Cause:** The application tried to commit a financial transaction (a "Credit Note reversal") where every line item had a value of zero. Accounting systems are designed to reject such transactions as they have no financial impact and are considered invalid.
* **What Went Wrong (Simple Terms):** The system tried to make an accounting entry, but the amount for the entry was $0.00. The accounting module correctly blocked this empty transaction, which caused the error.
* **To Investigate:**
* Check the application logic that creates credit note reversals. Why is it generating a transaction with only zero-value lines?
* Examine the specific credit note that was being reversed. Did it originally have a zero value, or was there a calculation error?
* **Severity:** HIGH
View raw incident details
Fingerprint: 531ffa396757
Occurrences: 1
2026-09-11T07:28:50.936242283Z [invoices] CN reversal posting failed: Error: Posting has no non-zero lines
Banchii · Log
1 log error(s) detected
Error
### Error 1: Failed to find Server Action * **Root Cause:** The Next.js server received a request to execute a specific server-side function (a "Server Action") that does not exist in the currently deployed code. This happens when a user's browser has an older version of the website loaded, and then a new version of the application is deployed to the server. The browser tries to call a function that has since been changed or removed. * **Explanation:** A…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-09 04:22:32 UTC
View full analysis
### Error 1: Failed to find Server Action
* **Root Cause:** The Next.js server received a request to execute a specific server-side function (a "Server Action") that does not exist in the currently deployed code. This happens when a user's browser has an older version of the website loaded, and then a new version of the application is deployed to the server. The browser tries to call a function that has since been changed or removed.
* **Explanation:** A user tried to perform an action (like submitting a form or clicking a button). Their browser sent a request using an outdated identifier for that action. The server, which is running newer code, did not recognize this old identifier and rejected the request.
* **Investigation:**
* Confirm if these errors cluster around the times of recent production deployments. If so, this is expected behavior for users who had the site open during the update.
* The immediate fix for an affected user is a hard refresh of the page.
* For a long-term solution, consider implementing a service worker or a pop-up banner that detects a new version and prompts the user to reload the page.
* **Severity:** **MEDIUM**. This breaks a feature for the affected user until they refresh the page, leading to a poor user experience. It does not represent a system-wide outage or data loss.
View raw incident details
Fingerprint: 2f6601b45394
Occurrences: 1
2026-09-09T04:21:28.536975099Z [Error: Failed to find Server Action "47d6c68fab044f44761ef4d902483e8dd54363de". This request might be from an older or newer deployment.
2026-09-09T04:21:28.537647499Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Banchii · Log
1 log error(s) detected
Error
### Error: Missing LINE Credentials * **Root Cause:** The application is missing the required `LINE_CHANNEL_SECRET` and `LINE_CHANNEL_ACCESS_TOKEN` environment variables needed to authenticate with the LINE Messaging API. * **What Went Wrong:** The application tried to use a feature involving the LINE messaging service, but it couldn't find the necessary "password" and "key" (the secret and token) to connect securely. * **How to Fix:** * Check the applica…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-07 01:57:06 UTC
View full analysis
### Error: Missing LINE Credentials
* **Root Cause:** The application is missing the required `LINE_CHANNEL_SECRET` and `LINE_CHANNEL_ACCESS_TOKEN` environment variables needed to authenticate with the LINE Messaging API.
* **What Went Wrong:** The application tried to use a feature involving the LINE messaging service, but it couldn't find the necessary "password" and "key" (the secret and token) to connect securely.
* **How to Fix:**
* Check the application's configuration or environment variables in the production environment.
* Ensure that `LINE_CHANNEL_SECRET` and `LINE_CHANNEL_ACCESS_TOKEN` are both present, spelled correctly, and have valid values from your LINE Developer account.
* If you recently deployed, confirm that these variables were included in the new deployment.
* **Severity:** HIGH. Any functionality related to LINE webhooks (like chatbots or notifications) is completely broken.
View raw incident details
Fingerprint: 2d67e9056535
Occurrences: 2
2026-09-07T01:56:09.749816678Z [LINE] webhook error: Error: LINE_CHANNEL_SECRET and LINE_CHANNEL_ACCESS_TOKEN must be set
Banchii · Log
1 log error(s) detected
Error
### Error 1: Failed to find Server Action * **Root Cause:** A version mismatch between the application code running in the user's browser and the code deployed on the server. The user's browser tried to execute a server-side function (a Next.js Server Action) that no longer exists or has been changed in the latest deployment. * **Simple Explanation:** The user was using an outdated version of the website in their browser tab. When they tried to perform an…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-05 02:02:53 UTC
View full analysis
### Error 1: Failed to find Server Action
* **Root Cause:** A version mismatch between the application code running in the user's browser and the code deployed on the server. The user's browser tried to execute a server-side function (a Next.js Server Action) that no longer exists or has been changed in the latest deployment.
* **Simple Explanation:** The user was using an outdated version of the website in their browser tab. When they tried to perform an action (like submitting a form), it failed because the server had already been updated and didn't recognize the old request.
* **Fix / Investigation:**
* This is often a temporary issue resolved by the user refreshing their page.
* Review caching headers for your HTML and JavaScript assets to ensure users receive new versions promptly after a deployment.
* Consider implementing a mechanism to detect a new version and prompt users to reload the application.
* **Severity:** **MEDIUM**. A specific feature failed for the user, but it doesn't indicate a system-wide outage and is often self-correcting.
View raw incident details
Fingerprint: ca854912c7e4
Occurrences: 1
2026-09-05T02:02:17.804376656Z [Error: Failed to find Server Action "89d14a718243acd1cb8c89d92951075e644aba67". This request might be from an older or newer deployment.
2026-09-05T02:02:17.805109758Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Banchii · Log
1 log error(s) detected
Error
### **Error 1: Failed to find Server Action** * **Root Cause**: The version of the application running in a user's browser is out of sync with the version running on the server. This typically happens when a new version of the application is deployed while a user has the old version open in their browser. The user's browser tries to call a function (a "Server Action") using an old ID, but the newly deployed server code no longer recognizes that specific I…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-03 18:35:38 UTC
View full analysis
### **Error 1: Failed to find Server Action**
* **Root Cause**: The version of the application running in a user's browser is out of sync with the version running on the server. This typically happens when a new version of the application is deployed while a user has the old version open in their browser. The user's browser tries to call a function (a "Server Action") using an old ID, but the newly deployed server code no longer recognizes that specific ID.
* **Simple Explanation**: The user's web page is like an old menu from a restaurant. They tried to order an item, but the server (the kitchen) has a new, updated menu and doesn't recognize the order. The requested action fails because it's from an outdated version of the page.
* **Potential Fixes**:
* This is often a temporary issue that users can fix by simply refreshing the page.
* Investigate your deployment process. Ensure that during a rollout, traffic is not sent to new servers from clients that still have old assets cached.
* Implement a long-term fix by adding a mechanism to your application that detects when a new version is available and prompts the user to reload the page.
* **Severity**: **MEDIUM**. This breaks a specific feature for users who are active during a deployment, leading to a failed action (e.g., a form submission failing). It is not a persistent bug but degrades the user experience.
View raw incident details
Fingerprint: fde831573a3d
Occurrences: 1
2026-09-03T18:34:26.573711589Z [Error: Failed to find Server Action "91f1a01dd1cbe0bb37fd1762634f649b87f66958". This request might be from an older or newer deployment.
2026-09-03T18:34:26.575201820Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Banchii · Log
1 log error(s) detected
Error
### **Error: Failed to find Server Action** * **Root Cause:** A mismatch exists between the application code running in the user's browser and the code running on the server. The browser tried to execute a server-side function (a "Server Action") that the current server deployment does not recognize, likely because the function was changed or removed in a recent update. * **Explanation:** The user had an old version of the website open in their browser wh…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-03 14:23:18 UTC
View full analysis
### **Error: Failed to find Server Action**
* **Root Cause:** A mismatch exists between the application code running in the user's browser and the code running on the server. The browser tried to execute a server-side function (a "Server Action") that the current server deployment does not recognize, likely because the function was changed or removed in a recent update.
* **Explanation:** The user had an old version of the website open in their browser when a new version was deployed to the server. When they tried to perform an action (like clicking a button or submitting a form), their browser sent an outdated command that the newly updated server no longer understands.
* **Investigation/Fixes:**
* This is often a temporary issue that users can resolve by simply refreshing the page.
* If this error occurs frequently, review your deployment process. Ensure that old application instances are gracefully retired and that traffic is not sent to new instances until they are fully ready.
* Check caching configurations (CDN, browser) to ensure users receive the latest application code promptly after a deployment.
* Consider implementing a feature to detect version mismatches and automatically prompt the user to reload the page.
* **Severity:** **MEDIUM**. This error breaks a specific feature for the user at that moment, leading to a failed action. However, it is typically not a persistent or application-wide failure and is often resolved with a page refresh.
View raw incident details
Fingerprint: 0a6385b0353a
Occurrences: 1
2026-09-03T14:22:44.595734368Z [Error: Failed to find Server Action "39ce5825b217b20f99cdae29ced5baefd2d6f704". This request might be from an older or newer deployment.
2026-09-03T14:22:44.596638348Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Banchii · Log
1 log error(s) detected
Error
### Error 1: Failed to find Server Action * **Root Cause:** A version mismatch between the code running in the user's browser and the code running on the server. This typically happens when the application is re-deployed while a user has the page open. The browser tries to call a specific server function (a "Server Action") that has changed or no longer exists in the new deployment. * **Explanation:** The user's browser was trying to perform an action usi…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-03 08:03:04 UTC
View full analysis
### Error 1: Failed to find Server Action
* **Root Cause:** A version mismatch between the code running in the user's browser and the code running on the server. This typically happens when the application is re-deployed while a user has the page open. The browser tries to call a specific server function (a "Server Action") that has changed or no longer exists in the new deployment.
* **Explanation:** The user's browser was trying to perform an action using an outdated "map" of the application. The server, having been updated to a newer version, couldn't find the location the old map was pointing to.
* **Potential Fixes:**
* This issue is usually temporary and resolved when the user refreshes their browser.
* If this error occurs frequently, review your deployment process. Ensure a clean cutover from old to new application versions, or consider implementing a "new version available, please refresh" banner for users.
* Check your CDN or web server caching rules to make sure users receive new frontend assets in a timely manner after a deployment.
* **Severity:** MEDIUM. The user's action fails, breaking a feature for them at that moment. However, it's not a system-wide outage and is typically self-correcting with a page refresh.
View raw incident details
Fingerprint: 291a11cdc26c
Occurrences: 1
2026-09-03T08:02:19.399348356Z [Error: Failed to find Server Action "d89a063a8034a8a771b49e32dd0e68a5e621b07b". This request might be from an older or newer deployment.
2026-09-03T08:02:19.399406082Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Banchii · Log
1 log error(s) detected
Error
### Error: DBD API returned 502 * **Root Cause:** The application made a request to a dependent service, referred to as the "DBD API", which was unavailable or returned an invalid response. A `502 Bad Gateway` error indicates a problem with an upstream service, not the application that logged the error. * **What Went Wrong (Simplified):** Your application tried to communicate with a helper service to get data or perform a task, but that helper service was…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-03 07:44:48 UTC
View full analysis
### Error: DBD API returned 502
* **Root Cause:** The application made a request to a dependent service, referred to as the "DBD API", which was unavailable or returned an invalid response. A `502 Bad Gateway` error indicates a problem with an upstream service, not the application that logged the error.
* **What Went Wrong (Simplified):** Your application tried to communicate with a helper service to get data or perform a task, but that helper service was offline or broken.
* **Investigation Steps:**
* Check the status and logs of the "DBD API" service to see why it is failing.
* Look for recent deployments to the "DBD API" that may have introduced a bug.
* Verify network connectivity between the main application and the "DBD API".
* **Severity:** HIGH (This likely means a core feature that relies on the "DBD API" is broken for users).
View raw incident details
Fingerprint: a571143c1c04
Occurrences: 3
2026-09-03T07:44:15.410303733Z [DBD] Error: Error: DBD API returned 502
Banchii · Log
1 log error(s) detected
Error
### **Error 1: Mismatched Application Versions** * **Root Cause:** A user's browser is running an older version of the application's front-end code, while the server has been updated with a newer version. The browser tried to execute a server-side function (a Next.js "Server Action") that no longer exists or has been changed in the new deployment. * **What Went Wrong:** In simple terms, the user's web page is out of date. It tried to ask the server to do…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-03 00:51:35 UTC
View full analysis
### **Error 1: Mismatched Application Versions**
* **Root Cause:** A user's browser is running an older version of the application's front-end code, while the server has been updated with a newer version. The browser tried to execute a server-side function (a Next.js "Server Action") that no longer exists or has been changed in the new deployment.
* **What Went Wrong:** In simple terms, the user's web page is out of date. It tried to ask the server to do something, but the server didn't understand the request because the "instructions" have changed since the user first loaded the page.
* **How to Fix:**
* **Immediate:** Users experiencing this can resolve it by performing a hard refresh of their browser page (e.g., Ctrl+Shift+R or Cmd+Shift+R).
* **Long-term:** Implement a version-checking mechanism that automatically prompts users to reload the page when a new version of the application is deployed.
* **Investigation:** Check your deployment process. Ensure that CDN caches are properly invalidated and that old server instances are cleanly replaced during a rollout.
* **Severity:** **HIGH**. This error prevents a user from completing an action and breaks application functionality, potentially on a critical path.
View raw incident details
Fingerprint: 6261d7a882fa
Occurrences: 1
2026-09-03T00:50:54.105063206Z [Error: Failed to find Server Action "5d2ed861c609ca2d10e1b8e4c1962c50f1aabd24". This request might be from an older or newer deployment.
2026-09-03T00:50:54.105132491Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Banchii · Log
1 log error(s) detected
Error
### Error 1: Failed to find Server Action * **Root Cause:** This Next.js error occurs when there's a version mismatch between the code running in the user's browser and the code running on the server. A user likely had the application open during a new deployment. When they triggered a "Server Action" (like submitting a form), their browser sent an ID for that action that the newly deployed server code no longer recognizes. * **Simple Explanation:** The w…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-03 00:25:22 UTC
View full analysis
### Error 1: Failed to find Server Action
* **Root Cause:** This Next.js error occurs when there's a version mismatch between the code running in the user's browser and the code running on the server. A user likely had the application open during a new deployment. When they triggered a "Server Action" (like submitting a form), their browser sent an ID for that action that the newly deployed server code no longer recognizes.
* **Simple Explanation:** The website was updated while a user had it open. When they tried to click a button or submit a form, their outdated page sent an old command that the new server code couldn't understand.
* **Potential Fixes:**
* Investigate implementing a version-checking mechanism that detects a mismatch and prompts the user to refresh the page.
* Ensure your deployment process properly invalidates caches (e.g., at the CDN level) to serve the latest assets.
* This error is often transient and resolves when the user reloads the page. Monitor its frequency to see if it's a persistent problem.
* **Severity:** HIGH
View raw incident details
Fingerprint: 795b3cd11c93
Occurrences: 1
2026-09-03T00:24:16.219130064Z [Error: Failed to find Server Action "45ef9efecc9032513425028beb3355fb2a7d22ce". This request might be from an older or newer deployment.
2026-09-03T00:24:16.220716165Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Banchii · Log
1 log error(s) detected
Error
### **Error 1: Mismatched Application Versions** * **Root Cause**: The error `Failed to find Server Action` indicates a version mismatch between the user's browser and the server. The user's browser is running an older version of the front-end code and tried to execute a server function that has changed or no longer exists in the newly deployed version on the server. This is common in modern web frameworks like Next.js. * **What Went Wrong**: A user tried…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-02 18:36:07 UTC
View full analysis
### **Error 1: Mismatched Application Versions**
* **Root Cause**: The error `Failed to find Server Action` indicates a version mismatch between the user's browser and the server. The user's browser is running an older version of the front-end code and tried to execute a server function that has changed or no longer exists in the newly deployed version on the server. This is common in modern web frameworks like Next.js.
* **What Went Wrong**: A user tried to perform an action (like clicking a button or submitting a form), but the server didn't recognize the instruction. This is because the application was updated on the server while the user had the page open in their browser.
* **To Investigate / Fix**:
* This issue typically resolves itself when the user reloads the page.
* For a better user experience, implement a global error handler that catches this specific error and prompts the user to refresh their page.
* Review your deployment strategy. If this error occurs frequently, it might suggest that users have very long sessions that are interrupted by frequent new deployments.
* **Severity**: **MEDIUM**. The feature is temporarily broken for the user, leading to a frustrating experience, but it does not cause a crash or data loss and is resolved with a page refresh.
View raw incident details
Fingerprint: 76f5efc53790
Occurrences: 1
2026-09-02T18:35:42.509259091Z [Error: Failed to find Server Action "58f9bc2119e49086081e062085c7ab6299135582". This request might be from an older or newer deployment.
2026-09-02T18:35:42.509939805Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Banchii · Log
1 log error(s) detected
Error
### Error 1: Failed to find Server Action * **Root Cause**: The user's browser tried to execute a server-side function (a Next.js Server Action) that doesn't exist on the currently deployed version of the server. This is a version mismatch, most likely because the user had the application open in their browser while a new version was deployed. * **Simple Explanation**: The user's web page was out of date. It tried to ask the server to perform an action, b…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-02 15:29:52 UTC
View full analysis
### Error 1: Failed to find Server Action
* **Root Cause**: The user's browser tried to execute a server-side function (a Next.js Server Action) that doesn't exist on the currently deployed version of the server. This is a version mismatch, most likely because the user had the application open in their browser while a new version was deployed.
* **Simple Explanation**: The user's web page was out of date. It tried to ask the server to perform an action, but the server had been updated with new instructions and didn't understand the old request.
* **Potential Fixes**:
* **Short-term**: This error is often temporary and can be resolved by the user simply refreshing their browser page to load the latest version of the application.
* **Long-term**: Implement a mechanism in the front-end to detect when a new version has been deployed and prompt the user with a "A new version is available, please refresh" banner.
* Review the application's deployment and caching strategy to minimize the time window where these mismatches can occur.
* **Severity**: **HIGH**. This error prevents a user from completing a specific action, potentially breaking a core feature of the application until the user manually refreshes.
View raw incident details
Fingerprint: 4621671e60fe
Occurrences: 1
2026-09-02T15:29:26.892247001Z [Error: Failed to find Server Action "6bfa9846bed5643e55331f2fbc31212dcb89617f". This request might be from an older or newer deployment.
2026-09-02T15:29:26.893813476Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Banchii · Log
1 log error(s) detected
Error
### **Error: Authentication Failure** * **Root Cause:** Insufficient context. The log explicitly flags an authentication error (`__isAuthError: true`), but provides no details about *why* it failed. This could be anything from an invalid password to an expired session token or a problem with an identity provider. * **Explanation:** The application registered a problem with a user's authentication. This means it could not verify who the user was or what th…
Status: Recorded
Occurrences: 1
Last seen: 2026-09-01 09:26:34 UTC
View full analysis
### **Error: Authentication Failure**
* **Root Cause:** Insufficient context. The log explicitly flags an authentication error (`__isAuthError: true`), but provides no details about *why* it failed. This could be anything from an invalid password to an expired session token or a problem with an identity provider.
* **Explanation:** The application registered a problem with a user's authentication. This means it could not verify who the user was or what they were allowed to do.
* **Investigation:**
* Examine the logs immediately surrounding this entry to see the full error message and stack trace.
* Identify which part of the application code produces this specific log message to understand the exact failure condition.
* Check the health of any external authentication services (e.g., Auth0, Okta, LDAP) or internal user databases.
* **Severity:** LOW
* **Note:** The confidence in this severity rating is low. This could represent a normal, expected event like a single user mistyping a password. However, if this error occurs frequently or for many users, it could indicate a CRITICAL system-wide login failure. More context is required to make a proper assessment.
View raw incident details
Fingerprint: 1a5c4ac4ed63
Occurrences: 2
2026-09-01T09:26:14.127216355Z __isAuthError: true,
Banchii · Log
1 log error(s) detected
Error
### Error 1: Failed to find Server Action * **Root Cause:** The application server, running on Next.js, received a request from a user's browser to execute a specific server-side function (a "Server Action" identified by a unique hash). The server could not find a function matching that ID. * **Simple Explanation:** A user's web browser was running an old version of the website's code, likely from before a recent deployment. When they tried to perform an…
Status: Recorded
Occurrences: 1
Last seen: 2026-08-29 05:21:16 UTC
View full analysis
### Error 1: Failed to find Server Action
* **Root Cause:** The application server, running on Next.js, received a request from a user's browser to execute a specific server-side function (a "Server Action" identified by a unique hash). The server could not find a function matching that ID.
* **Simple Explanation:** A user's web browser was running an old version of the website's code, likely from before a recent deployment. When they tried to perform an action (like submitting a form), their browser asked the newly updated server to run a function that no longer exists or has been renamed. The server, not recognizing the old function's ID, rejected the request.
* **Potential Fixes / Investigation:**
* This is often a temporary issue that resolves when the user reloads the page, which fetches the latest version of the application.
* Review the deployment process. If this error is frequent, consider implementing a mechanism to gracefully handle these version mismatches, such as forcing a page reload for users on old versions after a new deployment.
* If the error persists for users even after a refresh, investigate the build process to ensure all Server Actions are correctly compiled and deployed to all servers.
* **Severity:** **MEDIUM**. The user's action failed, interrupting their workflow. While not a critical crash or data loss, it breaks a feature until the user manually refreshes the page.
View raw incident details
Fingerprint: 9e5aebeb1531
Occurrences: 1
2026-08-29T05:20:56.608717135Z [Error: Failed to find Server Action "ef93c7d0ac3cfcf8c1c18e755f5a7d23aca7b9a9". This request might be from an older or newer deployment.
2026-08-29T05:20:56.609411599Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Banchii · Log
1 log error(s) detected
Error
### Error 1: Magic Link Email Delivery Failure * **Root Cause:** The application failed to authenticate with its third-party email sending service (e.g., SendGrid, Mailgun, AWS SES). The error code `EAUTH` indicates an authentication failure. * **Explanation:** When a user requested a "magic link" to log in, the system tried to send them an email. However, it failed because the credentials (like an API key or password) it uses to connect to the email serv…
Status: Recorded
Occurrences: 1
Last seen: 2026-08-20 10:13:44 UTC
View full analysis
### Error 1: Magic Link Email Delivery Failure
* **Root Cause:** The application failed to authenticate with its third-party email sending service (e.g., SendGrid, Mailgun, AWS SES). The error code `EAUTH` indicates an authentication failure.
* **Explanation:** When a user requested a "magic link" to log in, the system tried to send them an email. However, it failed because the credentials (like an API key or password) it uses to connect to the email service are incorrect, expired, or have been revoked.
* **Investigation Steps:**
* Check the environment variables or configuration files for the email service API key and other credentials.
* Verify that these credentials are still valid in the email provider's dashboard.
* Check the email provider's logs for more details on the failed authentication attempts.
* **Severity:** **HIGH**. This breaks a primary login method, preventing users from accessing their accounts.
View raw incident details
Fingerprint: 46bb1171cd39
Occurrences: 1
2026-08-20T10:13:19.916251213Z [auth.magic-link] email_delivery_failed { name: 'Error', code: 'EAUTH', command: 'API' }
Banchii · Health
Live health recovered
Info
Live endpoint recovered for Banchii
Status: Resolved
Occurrences: 1
Last seen: 2026-08-19 23:27:46 UTC
View raw incident details
Project: Banchii
Domain: app.banchii.com
Endpoint: Live
URL: https://app.banchii.com/api/health/live
Status: 200
Response time: 93ms
Recovered at: 2026-08-19T23:27:46.786489+00:00
Response: {"status":"ok","service":"banchii","accounting_revision":"woo-discount-vat-v2","environment":"production","timestamp":"2026-08-19T23:27:46.867Z"}
Banchii · Health
Live health check failed
Info
Live endpoint is failing for Banchii
Status: Resolved
Occurrences: 1
Last seen: 2026-08-19 23:27:46 UTC
View raw incident details
Project: Banchii
Domain: app.banchii.com
Endpoint: Live
URL: https://app.banchii.com/api/health/live
Status: no response
Response time: 26329ms
Consecutive failures: 2
Checked at: 2026-08-19T23:20:27.901622+00:00
Banchii · Log
2 log error(s) detected
Error
### Error 1: Failed to find Server Action * **Root Cause:** A version mismatch between the code running in the user's browser (client) and the code running on the server. This typically happens immediately after a new version of the application is deployed. * **Simple Explanation:** A user had an old version of the website open in their browser. When they clicked a button, their browser asked the server to perform an action that no longer exists in the ne…
Status: Recorded
Occurrences: 1
Last seen: 2026-08-17 06:53:32 UTC
View full analysis
### Error 1: Failed to find Server Action
* **Root Cause:** A version mismatch between the code running in the user's browser (client) and the code running on the server. This typically happens immediately after a new version of the application is deployed.
* **Simple Explanation:** A user had an old version of the website open in their browser. When they clicked a button, their browser asked the server to perform an action that no longer exists in the newly updated version of the application.
* **Potential Fixes:**
* This is often a temporary issue that resolves when the user reloads the page.
* Investigate implementing a "new version available" notification that prompts users to refresh.
* Review the deployment process to ensure smoother transitions and backwards compatibility for critical actions if possible.
* **Severity:** **MEDIUM**. The user's action failed, degrading their experience, but it's often a transient problem limited to users active during a deployment.
---
### Error 2: Router state header could not be parsed
* **Root Cause:** The server received a corrupted or malformed `Next-Router-State-Tree` HTTP header from the user's browser. This header is used by the Next.js framework to manage navigation between pages.
* **Simple Explanation:** When the user tried to navigate to a new page, their browser sent a garbled message to the server about the intended destination. The server couldn't understand the message and failed to load the page correctly.
* **Potential Fixes:**
* Check for bugs in client-side code that manipulates the URL or browser history.
* Investigate if a browser extension, proxy, or CDN is incorrectly modifying HTTP headers.
* Ensure the Next.js version is up-to-date, as this may be a known bug that has since been fixed.
* **Severity:** **HIGH**. This error breaks navigation, a core feature of the application, preventing users from moving between pages.
View raw incident details
Fingerprint: 0354b7d97802
Occurrences: 12
2026-08-17T06:52:19.259038252Z [Error: Failed to find Server Action "x". This request might be from an older or newer deployment.
2026-08-17T06:52:19.260640041Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
Fingerprint: 05e4fa3ff11f
Occurrences: 6
2026-08-17T06:52:56.357730642Z ⨯ Error: The router state header was sent but could not be parsed.
Banchii · Log
1 log error(s) detected
Error
### Error 1: Mismatched Server Action * **Root Cause:** This Next.js error, `Failed to find Server Action "x"`, signifies a version mismatch between the code running in the user's browser (the client) and the code running on the server. This most often occurs after a new deployment. * **What Went Wrong (Simplified):** A user loaded your website, then you updated the application. When the user tried to perform an action (like submitting a form), their brow…
Status: Recorded
Occurrences: 1
Last seen: 2026-08-14 12:29:13 UTC
View full analysis
### Error 1: Mismatched Server Action
* **Root Cause:** This Next.js error, `Failed to find Server Action "x"`, signifies a version mismatch between the code running in the user's browser (the client) and the code running on the server. This most often occurs after a new deployment.
* **What Went Wrong (Simplified):** A user loaded your website, then you updated the application. When the user tried to perform an action (like submitting a form), their browser sent a request that the new, updated server no longer recognizes because that action has been changed or removed.
* **Potential Fixes:**
* This is often a temporary problem that users can solve by simply refreshing the page.
* To prevent this, you can implement a client-side mechanism to detect when a new version is available and prompt the user to reload the page.
* Review your deployment and caching strategy. Ensure that CDNs and user browsers are not serving stale application code for extended periods after a new release.
* **Severity:** **MEDIUM**. This indicates a broken feature for affected users, leading to a frustrating experience. While it doesn't crash the application, it prevents users from completing tasks until they refresh.
View raw incident details
Fingerprint: 0354b7d97802
Occurrences: 11
2026-08-14T12:28:09.794555044Z [Error: Failed to find Server Action "x". This request might be from an older or newer deployment.
2026-08-14T12:28:09.795328287Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]