Couple weeks ago I’ve created a Command in Cursor to automatically report in awork a project.
This initially worked, but it stopped a week ago and I can’t fix it.
Running an agent ends with „Service unavailable“ for write tasks (retrieving data seems to work smoothly):
The awork API write path is currently returning 'Service unavailable' errors (reads still work).
Last week I’ve been receiving more concrete, but yet less understandable for me:
apparently the Cursor agent forgot to sent one required parameter and our validation was not great and ran then into an issue. I just fixed that and the fix should be online in 20 minutes. The intent parameter is now optional and the validation/responses improved. Thanks for reporting it.
Hi @Nils , thank you for your support, and I’m glad you were able to reproduce the issue!
Unfortunately, I wasn’t able yet to confirm the solution:
Report work time — partial run
Analysis completed, but no time entries were created. The awork MCP server returned 503 Service Unavailable on every write (POST /timeentries). Read operations (GET /me, GET /timeentries) worked fine.
I’ll let you know, if in next couple days I’ll be more lucky with using the agent.
If you need, I’ll be more than happy to send you the log files (not here, though, due to the data potentially contained).