1.9 KiB
1.9 KiB
DocFast Support Log
2026-02-16 20:17 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
2026-02-16 20:24 UTC
- Ticket #369 (dominik@superbros.tv): Lost API key → Replied with recovery flow instructions. Simple case.
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