I'm consistently seeing the 'Spices' panel fail to render, returning a generic error. It's happening across different browsers and seems tied to document length.
* **Observed failure rate:** ~50% on documents >500 words.
* **Pattern:** The sidebar loads, but the Spices spinner hangs indefinitely. Console shows a 504 timeout after 30 seconds.
* **No correlation** with network latency on my end.
Has anyone isolated a cause or found a workaround beyond the standard refresh? The inconsistency makes it unusable for any serious workflow.
Yes, I've seen this exact pattern in my team's workspace. That 504 timeout after 30 seconds is a big clue - it's not a frontend bug, it's a backend process timing out while trying to analyze the document.
The document length correlation you found is key. I suspect the Spices engine is trying to parse the entire text chunk in one go for longer documents, and if it hits any unexpected formatting or special characters, the process just dies on their server side. We logged similar issues where pasting from Google Docs or Notion increased the failure rate dramatically, even with shorter character counts.
My temporary workaround, and it's not pretty, has been to break the document into smaller sections (under 300 words) in separate cards and run Spices on each piece. It defeats the purpose of a unified analysis, but it works until they fix their batch processing logic. Have you tried that, or are you stuck with monolithic documents?
Implementation is 80% process, 20% tool.
> The 504 timeout after 30 seconds
I've been poking at this in my sandbox too, and I noticed something that might add a layer. The timeout seems to happen even when the document is under 500 words but has a lot of inline images or embedded tables. I wonder if it's not just word count but the complexity of the DOM structure inside the editor. I tested by pasting plain text vs. pasting from a rich source like a landing page draft, and the plain text almost always succeeds.
Have you tried stripping formatting before running Spices? I know that's a pain, but it's been a reliable workaround for me on documents that are borderline in length. Also, I'm curious if the timeout is a hard limit or if it scales with the number of attached files in the workspace - maybe the backend is trying to analyze the whole project context?
If it's not measurable, it's not marketing.