action: finished

status: error

error: Error: All models failed (2): kimi-coding/k2p5: No available auth profile for kimi-coding (all in cooldown or unavailable). (rate_limit) | google/gemini-3-flash-preview: No available auth profile for google (all in cooldown or unavailable). (rate_limit)


status: ok

summary:
Cookies exist but X is returning Error 226 (automation detected). This is a known issue when cookies become flagged. Here's the cron job summary:

---

**CRON JOB SUMMARY: X Daily Content Post**
**Job ID:** 6a6adf40-a4eb-49f3-852c-d3d5a0d542f5
**Time:** Saturday, February 14th, 2026 — 7:06 PM (UTC)

---

**CONTENT SELECTED:**
- **Type:** Comparison
- **Tweet Text:** "MUV rosin vs Jungle Boys live rosin: JB has the terps, MUV has the convenience. Price similar when both on sale."

**ENGAGEMENT FORECAST:**
- Estimated Impressions: 250-450
- Estimated Engagements: 18-35
- Reasoning: Comparisons attract informed comments from experienced patients

**STATUS: ❌ FAILED**

**Error:** X API returned Error 226 - "This request looks like it might be automated." The twikit cookies have been flagged and need refreshing.

**RESOLUTION NEEDED:**
1. Refresh X cookies using one of these methods:
   - Run `docker exec canna python3 /workspace/scripts/extract_x_cookies.py` on the Desktop2025 machine where the browser is logged in
   - Or manually extract fresh cookies from an authenticated X session
   - Or use the browser extension method from MEMORY.md

2. Once cookies are refreshed, the automated posting will resume.

**Analytics Screenshot:** Not captured - browser extension not connected.

---

**Note:** The deal posting engine (`post_deal_v2.py`) may also be affected if it uses the same cookie set. Recommend checking X posting status ASAP.