Asana’s API docs mention that “Changes in Asana (regardless of whether they’re made though the web product or the API) are forwarded to our search infrastructure to be indexed. This process can take between 10 and 60 seconds to complete under normal operation, and longer during some production incidents. Making a change to a task that would alter its presence in a particular search query will not be reflected immediately.”
Does this impact only my ability to get a complete list of the tasks I am searching for, if one had just been created for example? what about changes made to the task, can I see these changes that had just been implemented when I ‘get’ this task through the api?
I don’t feel like such lag exists in the web product, should I expect a similar performance between the API and the web product as the docs say?
I don’t really see a lag either, except in some specific cases. I would assume the lag is the same between web and API, and I am also guessing they want to protect themselves by advertising such a lag even though there is usually none.
@Phil_Seeman what do you think?
1 Like
This refers to the
GET /workspaces/{workspace_gid}/tasks/search
endpoint specifically, and not to any of the others.
I’ve seen lags in the Advanced Search in the UI and expect that’s the same as in this specific endpoint too, as stated.
Hope that helps,
Larry
I don’t use the search API so I can’t provide any input here, sorry.
I do see lag when looking for task to be marked blocked by for example, can take several seconds to index for example.