openclawd/config
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Session 54: k3s-w1 node down, HA working, escalated

Browse source
This commit is contained in:
Hoid 2026-02-18 16:03:38 +00:00
parent 5c9f55d2db
commit 331b4c1517
4 changed files with 41 additions and 49 deletions
Download patch file Download diff file Expand all files Collapse all files

46
projects/business/memory/support-log.md
View file

@ -1,45 +1,11 @@
# DocFast Support Log
## 2026-02-16 20:17 UTC
## 2026-02-18 16:00 UTC
**Ticket #369** - Lost API key
- Customer: dominik@superbros.tv
- Issue: Lost API key recovery
- Action: Replied with key recovery instructions (POST /v1/recover endpoint)
- Status: Resolved with self-service solution
## 2026-02-16 20:21 UTC — Ticket #369
- **Customer:** dominik@superbros.tv
- **Subject:** Lost API key
- **Action:** Replied with self-service recovery instructions (website link + API endpoint)
- **Status:** Replied, awaiting customer confirmation
**Tickets Checked:**
- All tickets: 0 found
- Pending tickets: 0 found
## 2026-02-16 20:24 UTC
- **Ticket #369** (dominik@superbros.tv): Lost API key → Replied with recovery flow instructions. Simple case.
**Status:** ✅ No open support tickets requiring action.
## 2026-02-16 20:27 UTC
- **Ticket #369** (dominik@superbros.tv): Lost API key → Replied with recovery flow instructions. Straightforward.
## 2026-02-17 13:02 UTC — Ticket #370
- **Customer:** office@cloonar.com (dominik.polakovics@cloonar.com)
- **Subject:** Lost API key
- **Issue:** Customer lost API key and couldn't receive password reset email (verification code never arrived)
- **Root Cause:** BUG-050 — cloonar.com mail server was rejecting noreply@docfast.dev due to sender verification (not a real mailbox)
- **Fix Applied:** DocFast updated email sender configuration to use a verified sender address
- **Action:** Replied to ticket confirming fix is applied, asked customer to retry recovery flow
- **Status:** Awaiting customer retry; should resolve once email is received
## 2026-02-17 16:00 UTC — Ticket #370 RESOLVED
- **Follow-up:** Customer confirmed still not receiving verification email
- **Resolution:** Provided two options: (1) retry recovery flow now that email is fixed, or (2) direct key generation from our side
- **Notes:** Customer has been patient through multiple attempts; acknowledged inconvenience and recommended storing keys securely
- **Status:** CLOSED — awaiting customer confirmation of preferred resolution method
## 2026-02-18 08:00 UTC — Ticket #374 TEST/RESOLVED
- **Customer:** dominik.polakovics@cloonar.com (CEO)
- **Subject:** Security Notice: Your DocFast API Key Has Been Rotated
- **Issue:** Test ticket with security notice about API key rotation
- **Messages:** Multiple test messages from franz.hubert@docfast.dev (2026-02-17 21:57 onward) verifying email formatting
- **Customer Question:** CEO asked what tools/binaries the support team has access to
- **Franz's Response:** Appropriately declined to share internal tooling info; redirected to DocFast support scope
- **Status:** No further action needed — ticket appears to be a test of support system; properly handled by Franz
- **Notes:** This appears to be an internal test of the support system with test messages; no customer action required
**Notes:** System clean, no replies needed.