Watchtower Control Room

My Thai Doctor Admin

Monitor connected apps, review incidents, onboard new projects, and keep your operational contract in one calm place.

Add Project Integration Guide
production

My Thai Doctor Admin

Healthy

https://admin.mythaidoctor.com

Container Pattern
adminmythaidoctor
Source
Manual
Container
my-thai-doctor-adminmythai....6zyhpnuceddpk7y0d7r0cqivq
Last Alert
2026-07-16 12:48:22 UTC
Open Errors
0
Open Warnings
0
Info Events
0
Monitoring
Active
Edit project Implementation guide
Health

Endpoint Snapshot

LIVE

https://admin.mythaidoctor.com/api/health/live

Healthy
Status Code
200
Response Time
65 ms
Failures
0

Last checked: 2026-07-17 09:08:06 UTC

READY

https://admin.mythaidoctor.com/api/health/ready

Healthy
Status Code
200
Response Time
212 ms
Failures
0

Last checked: 2026-07-17 09:08:06 UTC

Recent Alerts

My Thai Doctor Admin Incident Feed

My Thai Doctor Admin · Log

1 log error(s) detected

Error
### Error 1: Failed to find Server Action * **Root Cause:** The Next.js backend received a request from a user's browser to execute a specific server-side function (a "Server Action"), but the running application version on the server does not contain a function with the matching ID. This is a classic version mismatch issue. * **What Went Wrong (Simplified):** A user's web browser was out of sync with the server. This typically happens right after a new v…
Status: Recorded Occurrences: 1 Last seen: 2026-07-16 12:48:36 UTC
View full analysis
### Error 1: Failed to find Server Action * **Root Cause:** The Next.js backend received a request from a user's browser to execute a specific server-side function (a "Server Action"), but the running application version on the server does not contain a function with the matching ID. This is a classic version mismatch issue. * **What Went Wrong (Simplified):** A user's web browser was out of sync with the server. This typically happens right after a new version of the application is deployed. The user's browser tried to perform an action (like submitting a form) using old instructions that the newly updated server no longer understood. * **Potential Fixes / Investigation:** * **Immediate User Fix:** The user can likely resolve this by performing a hard refresh of the page (Ctrl+Shift+R on Windows/Linux, Cmd+Shift+R on Mac). * **Deployment Process:** Review your deployment and caching strategy. Ensure that both server code and client-side JavaScript are deployed and updated for users at the same time to prevent this mismatch. * **Cache Invalidation:** Ensure your CDN and browser caching rules are not too aggressive, which could cause users to be stuck on an old version of the frontend after a backend update. * **Severity:** **HIGH**. This error indicates that a core feature initiated by a user failed completely. While often temporary and fixable with a refresh, it directly impacts user functionality.
View raw incident details 
Fingerprint: 0a1e69ca5ffb
Occurrences: 1

2026-07-16T12:48:21.251270122Z [Error: Failed to find Server Action "e96e8c6d4143a3a44ee6daaddd6cd978aa415fe8". This request might be from an older or newer deployment.
2026-07-16T12:48:21.251331675Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
My Thai Doctor Admin · Log

1 log error(s) detected

Error
### **Error: Failed to find Server Action** * **Root Cause:** The user's browser is running an old version of the application's code, likely from before a recent deployment. The server has been updated with a new version of the code. When the user tried to perform an action (e.g., submitting a form), their browser sent a request to the server referencing a function by an ID (`eafd54...`) that existed in the old code but has been changed or removed in the…
Status: Recorded Occurrences: 1 Last seen: 2026-07-15 23:19:21 UTC
View full analysis
### **Error: Failed to find Server Action** * **Root Cause:** The user's browser is running an old version of the application's code, likely from before a recent deployment. The server has been updated with a new version of the code. When the user tried to perform an action (e.g., submitting a form), their browser sent a request to the server referencing a function by an ID (`eafd54...`) that existed in the old code but has been changed or removed in the new code. * **Simple Explanation:** A user had the admin panel open in their browser while a new software update was released. When they tried to click a button or save something, their old version of the page asked the newly updated server to do a task that no longer exists, causing an error. * **Potential Fixes / Investigation:** * **Immediate User Fix:** The affected user can resolve this by performing a hard refresh of the page (Ctrl+Shift+R or Cmd+Shift+R). * **Long-Term Solution:** Implement a mechanism to prompt users to reload the page when a new version of the application is deployed. * **Investigation:** Correlate the timestamp of this error with your deployment logs. A recent deployment just before the error would confirm this root cause. * **Severity:** **HIGH** * While not a system-wide outage, this error prevents users from performing key actions until they manually refresh their page, potentially blocking important administrative tasks.
View raw incident details 
Fingerprint: 7d6f73a6869a
Occurrences: 1

2026-07-15T23:18:15.196264244Z [Error: Failed to find Server Action "eafd54aff58cc948cfbfa4e2327faebc7b290c66". This request might be from an older or newer deployment.
2026-07-15T23:18:15.196310453Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
My Thai Doctor Admin · Log

1 log error(s) detected

Error
### Error 1: Mismatched Application Versions * **Root Cause:** The server received a request from a user's browser to execute a specific function (a Next.js "Server Action"), but the server-side code has no record of that function's ID. * **Explanation:** This happens when the version of the application running in the user's browser is out of sync with the version running on the server. For example, you deployed a new update, but the user still had the ol…
Status: Recorded Occurrences: 1 Last seen: 2026-07-03 12:48:34 UTC
View full analysis
### Error 1: Mismatched Application Versions * **Root Cause:** The server received a request from a user's browser to execute a specific function (a Next.js "Server Action"), but the server-side code has no record of that function's ID. * **Explanation:** This happens when the version of the application running in the user's browser is out of sync with the version running on the server. For example, you deployed a new update, but the user still had the old version of the site open in their browser. When they tried to perform an action (like submitting a form), the old code sent a request that the new server no longer recognizes. * **Investigation/Fixes:** * The user can almost always fix this by simply reloading the page. * Verify if a new deployment occurred around the time of the error (`2026-07-03 12:47 UTC`). If so, this is expected, transient behavior. * If this error happens frequently outside of deployment windows, investigate caching layers (like a CDN) that might be serving stale frontend code, or potential inconsistencies in the build process across servers. * **Severity:** **MEDIUM**. The action the user tried to perform failed, breaking a feature for them at that moment. However, it is usually a temporary problem resolved by a page refresh and not a systemic crash.
View raw incident details 
Fingerprint: d5cdf75041e4
Occurrences: 1

2026-07-03T12:47:36.732784926Z [Error: Failed to find Server Action "e0ade06127ad702a0d12fecabe873b6d82b30d4b". This request might be from an older or newer deployment.
2026-07-03T12:47:36.733484398Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
My Thai Doctor Admin · Health

Ready health recovered

Info
Ready endpoint recovered for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:35:38 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Ready
URL: https://admin.mythaidoctor.com/api/health/ready
Status: 200
Response time: 549ms
Recovered at: 2026-06-24T10:35:37.473841+00:00
Response: {"status":"ok","service":"mythaidoctor-admin","timestamp":"2026-06-24T10:35:38.017Z","checks":{"env":"ok","database":"ok"},"missing_env_vars":[],"database_error":null}
My Thai Doctor Admin · Health

Ready health check failed

Info
Ready endpoint is failing for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:35:38 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Ready
URL: https://admin.mythaidoctor.com/api/health/ready
Status: no response
Response time: 10998ms
Consecutive failures: 2
Checked at: 2026-06-24T10:32:04.473796+00:00
My Thai Doctor Admin · Health

Ready health recovered

Info
Ready endpoint recovered for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:29:54 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Ready
URL: https://admin.mythaidoctor.com/api/health/ready
Status: 200
Response time: 379ms
Recovered at: 2026-06-24T10:29:53.475422+00:00
Response: {"status":"ok","service":"mythaidoctor-admin","timestamp":"2026-06-24T10:29:53.848Z","checks":{"env":"ok","database":"ok"},"missing_env_vars":[],"database_error":null}
My Thai Doctor Admin · Health

Ready health check failed

Info
Ready endpoint is failing for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:29:54 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Ready
URL: https://admin.mythaidoctor.com/api/health/ready
Status: no response
Response time: 10284ms
Consecutive failures: 2
Checked at: 2026-06-24T10:27:32.186134+00:00
My Thai Doctor Admin · Health

Live health recovered

Info
Live endpoint recovered for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:29:53 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Live
URL: https://admin.mythaidoctor.com/api/health/live
Status: 200
Response time: 70ms
Recovered at: 2026-06-24T10:29:53.475017+00:00
Response: {"status":"ok","service":"mythaidoctor-admin","environment":"production","timestamp":"2026-06-24T10:29:53.538Z"}
My Thai Doctor Admin · Health

Live health check failed

Info
Live endpoint is failing for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:29:53 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Live
URL: https://admin.mythaidoctor.com/api/health/live
Status: no response
Response time: 10999ms
Consecutive failures: 2
Checked at: 2026-06-24T10:26:20.471612+00:00
My Thai Doctor Admin · Health

Ready health recovered

Info
Ready endpoint recovered for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:23:08 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Ready
URL: https://admin.mythaidoctor.com/api/health/ready
Status: 200
Response time: 427ms
Recovered at: 2026-06-24T10:23:08.006993+00:00
Response: {"status":"ok","service":"mythaidoctor-admin","timestamp":"2026-06-24T10:23:08.425Z","checks":{"env":"ok","database":"ok"},"missing_env_vars":[],"database_error":null}
My Thai Doctor Admin · Health

Ready health check failed

Info
Ready endpoint is failing for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:23:08 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Ready
URL: https://admin.mythaidoctor.com/api/health/ready
Status: no response
Response time: 10996ms
Consecutive failures: 2
Checked at: 2026-06-24T10:21:56.474136+00:00
My Thai Doctor Admin · Health

Ready health recovered

Info
Ready endpoint recovered for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:18:45 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Ready
URL: https://admin.mythaidoctor.com/api/health/ready
Status: 200
Response time: 528ms
Recovered at: 2026-06-24T10:18:44.638868+00:00
Response: {"status":"ok","service":"mythaidoctor-admin","timestamp":"2026-06-24T10:18:45.125Z","checks":{"env":"ok","database":"ok"},"missing_env_vars":[],"database_error":null}
My Thai Doctor Admin · Health

Ready health check failed

Info
Ready endpoint is failing for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:18:45 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Ready
URL: https://admin.mythaidoctor.com/api/health/ready
Status: no response
Response time: 10998ms
Consecutive failures: 2
Checked at: 2026-06-24T10:17:33.472947+00:00
My Thai Doctor Admin · Health

Live health recovered

Info
Live endpoint recovered for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:09:47 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Live
URL: https://admin.mythaidoctor.com/api/health/live
Status: 200
Response time: 97ms
Recovered at: 2026-06-24T10:09:46.862147+00:00
Response: {"status":"ok","service":"mythaidoctor-admin","environment":"production","timestamp":"2026-06-24T10:09:46.952Z"}
My Thai Doctor Admin · Health

Live health check failed

Info
Live endpoint is failing for My Thai Doctor Admin
Status: Resolved Occurrences: 2 Last seen: 2026-06-24 10:09:47 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Live
URL: https://admin.mythaidoctor.com/api/health/live
Status: no response
Response time: 10585ms
Consecutive failures: 2
Checked at: 2026-06-24T10:07:24.885663+00:00
My Thai Doctor Admin · Health

Ready health recovered

Info
Ready endpoint recovered for My Thai Doctor Admin
Status: Resolved Occurrences: 1 Last seen: 2026-06-24 10:08:46 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Ready
URL: https://admin.mythaidoctor.com/api/health/ready
Status: 200
Response time: 636ms
Recovered at: 2026-06-24T10:08:35.900958+00:00
Response: {"status":"ok","service":"mythaidoctor-admin","timestamp":"2026-06-24T10:08:36.531Z","checks":{"env":"ok","database":"ok"},"missing_env_vars":[],"database_error":null}
My Thai Doctor Admin · Health

Ready health check failed

Info
Ready endpoint is failing for My Thai Doctor Admin
Status: Resolved Occurrences: 2 Last seen: 2026-06-24 10:08:46 UTC
View raw incident details 
Project: My Thai Doctor Admin
Domain: admin.mythaidoctor.com
Endpoint: Ready
URL: https://admin.mythaidoctor.com/api/health/ready
Status: no response
Response time: 10996ms
Consecutive failures: 2
Checked at: 2026-06-24T10:03:59.474936+00:00
My Thai Doctor Admin · Log

2 log error(s) detected

Error
### **Error: Failed to find Server Action** * **Root Cause:** A version mismatch occurred between the user's web browser and the application server. This typically happens right after a new version of the application has been deployed. The user's browser, holding an older version of the site, tried to execute an action (like submitting a form) that the newly updated server no longer recognizes by its old ID. * **Simple Explanation:** The user had the webs…
Status: Recorded Occurrences: 1 Last seen: 2026-06-18 03:58:00 UTC
View full analysis
### **Error: Failed to find Server Action** * **Root Cause:** A version mismatch occurred between the user's web browser and the application server. This typically happens right after a new version of the application has been deployed. The user's browser, holding an older version of the site, tried to execute an action (like submitting a form) that the newly updated server no longer recognizes by its old ID. * **Simple Explanation:** The user had the website open while it was being updated. When they tried to do something, their old version of the page tried to talk to the new version on our server, but the server didn't understand the command because it had changed. * **Investigation & Fixes:** * **Monitor deployment times:** Check if these errors cluster immediately after a new deployment. If so, this is expected but can be improved. * **Improve user experience:** Implement a "new version available" notification that prompts users to refresh the page after a deployment. * **Review caching:** Check your CDN and server caching rules (`Cache-Control` headers) to ensure users get the latest application code more quickly after an update. Overly aggressive caching can make this problem worse. * **Severity:** **HIGH**. This error indicates that a core feature is broken for the user until they manually refresh their page, preventing them from completing their task.
View raw incident details 
Fingerprint: d2fa0fcc7f3f
Occurrences: 1

2026-06-18T03:57:15.092421782Z [Error: Failed to find Server Action "c90ff1acf5e053ef6acf7e1bbb48737b073f7363". This request might be from an older or newer deployment.
2026-06-18T03:57:15.092496825Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]

Fingerprint: 759d187dc9ff
Occurrences: 1

2026-06-18T03:57:16.119104130Z [Error: Failed to find Server Action "47740cc88fcc0926ce4b1aaacd901eb8a2efb486". This request might be from an older or newer deployment.
2026-06-18T03:57:16.119171092Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
My Thai Doctor Admin · Log

1 log error(s) detected

Error
### Error 1: Failed to find Server Action * **Root Cause:** A mismatch between the application code running in a user's browser and the code running on the server. This happens when a new version of the application is deployed while a user has an older version of the site open. The browser attempts to call a server function (a "Server Action") that has been changed or removed in the new deployment. * **What Went Wrong (Simplified):** A user tried to perfo…
Status: Recorded Occurrences: 1 Last seen: 2026-06-17 18:49:46 UTC
View full analysis
### Error 1: Failed to find Server Action * **Root Cause:** A mismatch between the application code running in a user's browser and the code running on the server. This happens when a new version of the application is deployed while a user has an older version of the site open. The browser attempts to call a server function (a "Server Action") that has been changed or removed in the new deployment. * **What Went Wrong (Simplified):** A user tried to perform an action (like clicking a button or submitting a form) using an outdated version of the webpage. The server, which had already been updated with new code, didn't recognize the request from the old page. * **Potential Fixes:** * The user can resolve this by simply refreshing their browser page to load the latest code. * To prevent this, implement a mechanism to notify users when a new version is available and prompt them to refresh. * Review the deployment process to ensure old assets are properly invalidated. * **Severity:** **MEDIUM**. A specific user action failed, which can be frustrating and break a workflow. However, it is not a site-wide outage and is resolved by a simple page refresh.
View raw incident details 
Fingerprint: 23b1903a3cfe
Occurrences: 1

2026-06-17T18:49:27.281336620Z [Error: Failed to find Server Action "8faadaf3bf8f4675ab8a7333c38114ee30cb184e". This request might be from an older or newer deployment.
2026-06-17T18:49:27.281449831Z Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
My Thai Doctor Admin · Log

3 log error(s) detected

Error
- Root cause: AI analysis is temporarily unavailable, so Watchtower is sending a basic fallback summary. - Distinct errors: 3 - First signal: 2026-06-08T23:37:26.611782077Z E, [2026-06-08T23:37:26.611553 #1] ERROR -- : [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] - Recommended action: review the raw log excerpt below and try the analysis again later if needed. AI error: 400 INVALID_ARGUMENT. {'error': {'code': 400, 'message': 'API Key not found. Please pass a v…
Status: Recorded Occurrences: 1 Last seen: 2026-06-08 23:38:17 UTC
View full analysis
- Root cause: AI analysis is temporarily unavailable, so Watchtower is sending a basic fallback summary. - Distinct errors: 3 - First signal: 2026-06-08T23:37:26.611782077Z E, [2026-06-08T23:37:26.611553 #1] ERROR -- : [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] - Recommended action: review the raw log excerpt below and try the analysis again later if needed. AI error: 400 INVALID_ARGUMENT. {'error': {'code': 400, 'message': 'API Key not found. Please pass a valid API key.', 'status': 'INVALID_ARGUMENT', 'details': [{'@type': 'type.googleapis.com/google.rpc.ErrorInfo', 'reason': 'API_KEY_INVALID', 'domain': 'googleapis.com', 'metadata': {'service': 'generativelanguage.googleapis.com'}}, {'@type': 'type.googleapis.com/google.rpc.LocalizedMessage', 'locale': 'en-US', 'message': 'API Key not found. Please pass a valid API key.'}]}} Raw errors: --- Error 1 --- 2026-06-08T23:37:26.611782077Z E, [2026-06-08T23:37:26.611553 #1] ERROR -- : [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] 2026-06-08T23:37:26.611837800Z [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] ActionController::RoutingError (No route matches [GET] "/sitemap.xml"): --- Error 2 --- 2026-06-08T23:37:26.611852392Z [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] actionpack (8.0.2.1) lib/action_dispatch/middleware/debug_exceptions.rb:35:in 'ActionDispatch::DebugExceptions#call' 2026-06-08T23:37:26.611858151Z [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] actionpack (8.0.2.1) lib/action_dispatch/middleware/show_exceptions.rb:32:in 'ActionDispatch::ShowExceptions#call' --- Error 3 --- 2026-06-08T23:37:26.629479372Z I, [2026-06-08T23:37:26.629257 #1] INFO -- : [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] {"method":"GET","format":"*/*","controller":"ErrorsController","action":"show","status":404,"allocations":647,"duration":11.56,"view":0.14,"db":0.0,"host":"sign.mythaidoctor.com","fwd":"172.68.189.187","params":{},"uid":null,"aid":null,"rid":null,"raid":null}
View raw incident details 
Fingerprint: 0a1c70c6f08f
Occurrences: 1

2026-06-08T23:37:26.611782077Z E, [2026-06-08T23:37:26.611553 #1] ERROR -- : [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90]   
2026-06-08T23:37:26.611837800Z [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] ActionController::RoutingError (No route matches [GET] "/sitemap.xml"):

Fingerprint: 6c3a657ae451
Occurrences: 1

2026-06-08T23:37:26.611852392Z [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] actionpack (8.0.2.1) lib/action_dispatch/middleware/debug_exceptions.rb:35:in 'ActionDispatch::DebugExceptions#call'
2026-06-08T23:37:26.611858151Z [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] actionpack (8.0.2.1) lib/action_dispatch/middleware/show_exceptions.rb:32:in 'ActionDispatch::ShowExceptions#call'

Fingerprint: 45d8b5def431
Occurrences: 1

2026-06-08T23:37:26.629479372Z I, [2026-06-08T23:37:26.629257 #1]  INFO -- : [a8304bfb-c8e2-40ff-90ec-bf7255fdbe90] {"method":"GET","format":"*/*","controller":"ErrorsController","action":"show","status":404,"allocations":647,"duration":11.56,"view":0.14,"db":0.0,"host":"sign.mythaidoctor.com","fwd":"172.68.189.187","params":{},"uid":null,"aid":null,"rid":null,"raid":null}