204 no content on tasks endpoint

[Nicolas Peric]

Hi everyone,

I'm using the tasks  endpoint on the API to retrieve time tracked by spaceId and from, to dates.

I've been using it without any issues with around 6 spaces until today that I've been granted access to a new space that's responding with 204 no content.

- I have owner access so pretty sure it's not something with the API credentials
- I can see tasks from the Assembla frontend on the same dates I'm using on the API so I'm sure tasks exist on the selected dates

Wasn't able to find any configs on the space settings that could block API access on the Tasks tool. Everything seems fine, even the team Advanced Tools Permissions is set to default on all team members for the Tasks tool.

Are you guys aware about any config that could force a 204 No content response on tasks for a space? I'm not seeing anything wrong on the request and if I retrieve tasks on another spaces that works i.e on a Sunday the response is also 204 since no time was tracked that day (it seems OK). 

Thanks in advance!

Nico

[Nicolas Peric]

Hello again,

Without any changes on the space or the user access I've been using with the API the tasks endpoint started working correctly. It seems the tasks API endpoint might have a bug : (

This was failing with a user that was already assigned to the space so I don't believe it's related to a delay on permissions propagation (since my user was added to the team for API testing purposes).

Can't delete the conversation but maybe it helps others knowing a 204 no content response on tasks is not 100% reliable

Regards,

Nico