🪲 Bugs
Open

Capacities/TickTick Task Action Failure as of Sep 1

My Capacities/TickTick task action was working normally until approximately September 1–2, 2026. It now fails every time with:

Status: 500

errorCode: "unknown"

errorId: 9qk6agaq@erver-14 (the error box cuts off here and will not expand)

I have:

  • Deleted and reconnected the TickTick integration.
  • Confirmed that the TickTick connection shows Active.
  • Confirmed that the TickTick task action shows Active.
  • Confirmed that the action is configured to send tasks to my TickTick Inbox.
  • Created a brand-new, simple test task in Capacities, which produces the same error.
  • Confirmed that I can manually create tasks in my TickTick Inbox, so TickTick itself is functioning.

Could you please check the server logs for this error and determine why the Capacities → TickTick task creation request is returning HTTP 500? I noticed that the old Capacities Public API Beta was discontinued on September 1, 2026, so I wonder whether this could be related to a recent backend change, although I realize the native TickTick integration may be separate from that API.

3 Comments

Sign in to comment

LM
Luis Martin
Luis Martin·2 months ago

Hi Justine Michaudel ,

It seems to be solved already, could you try setting up the integration once again? maybe switching the List the ticktick Task Action is set to?

If it still doesn't work please let me know

LM
Luis Martin
Luis Martin·2 months ago

Hi Justine Michaudel ,

Thank you for reporting! The issue seems to be on TickTick's side. We'll keep this ticket open until we can confirm it's fully corrected.

TC
Team Capacities
Team Capacities·2 months ago

Please add the exact time and timezone of one recent failure, plus your platform and Capacities app version. Also confirm whether the failure occurs in every space or only one; the error ID and HTTP 500 are useful for log investigation. https://docs.capacities.io/reference/task-actions

This reply was written by the Capacities AI Assistant. Please note AI may make mistakes. If this response doesn't resolve your question or issue and the community can't help either, feel free to reach out to us at