Hi, YES we could resolve the issue.
We were working with the FREE account, then when we moved to a paid plan, we could do more tests/scenarios.
We found that bug, it was related to the Asana SDK.
We updated the version and the problem was solved.
HTH.
I updated to 1.0.2 and still get this āCannot create Collection from response that does not have resourcesāā¦
@Lamine did you change anything in the sdk or just update it? I might have to downgrade to earlier version. Do you know what version that worked for you?
Did you manage to find anything?
This is the code im using
also creating the client with retryOnRateLimit: true so shouldnt be a rate limit issue.
{retryOnRateLimit: true,}
Her is an example of the code. It loops over it for a while. then i sudden
const getTasksOfProject = gid =>
client.tasks
.findByProject(gid, {})
.then(collection => {
collection.stream().on('data', task => {
return updateTask(task);
});
collection.stream().on('error', err => {
console.log(err);
throw new Error(err.value);
});
})
.catch(err=> {
throw new Error(err.value);
});
Any help would be appreciated. Might have to write my own loop for it. But would prefer if the sdk worked 
not really, my code breaks sometimes in a middle of the day. I have a 100 functions running every X minutes, so overall it works great, just breaks sometimes, making it hard to debug I am afraid ^^
Yeah was mostly joking about the sdk being broken. Ive been using it extensivly for 5 years. But yeah the errors/stack trace from the sdk could be better. Im gonna try to change the opt-fields and see if i can find where the error starts happening. I cant have the code breaking. 
@Jonas_O
did you change anything in the sdk or just update it? I might have to downgrade to earlier version. Do you know what version that worked for you?
Version 1.0.0 + package named api v. 5.0.7
I have the same problem while fetching the tags from the project.
Cannot create a Collection from the response that does not have resources.
Sometimes it works. Sometimes it returns this error.
And I think the code that breaks is actually within the Asana client itself. @sasha_f in case you want to investigate or raise a bugā¦
Sporadically getting this error, now, too. rate limiting doesnāt seem to matter at all (Iām using p-throttle to manage that within my app). It just happens at totally random times.