The result is too large. You should use pagination (may require specifying a workspace)!

[Sam_Hoffman]

I am trying to export project info as JSON. I am getting this error message, presumably because there is too much data:

{
“errors” : [ {
“message” : “The result is too large. You should use pagination (may require specifying a workspace)!”,
“help” : “For more information on API status codes and how to handle them, read the docs on errors: Build an app with Asana”
} ]
}

Not sure what this means or what I need to do to get this file exported. Any ideas?

Note: I have almost no coding knowledge, so please keep that in mind when offering help. Thanks!

[Bastien_Siebman]

Hi,

That should help: Build an app with Asana
If it is unclear, don’t hesitate to come back here

Bastien
a-superheroes.com

[abass]

I too just started getting this and it makes no sense because I am using the Zapier integration of Asana, which has no pagination API options within it.

I’m defining the workspace and the project so it shouldn’t be having issues?

I have been totally fine with this integration for over a year now, and now it’s out of control with this same error. Any ideas? Is this something that Zapier needs to get involved on?

Thanks!
Alex

[Bastien_Siebman]

I think the issue is exactly what the message says: the requests Zapier is doing are getting too many results and Zapier needs to use pagination… which means Zapier (or Asana?!) should fix the zaps

[abass]

Hey man, yeah it definitely sounds that way. This was the reply that I got from Zapier:

Thanks for writing in, and I’m so sorry for the headache here!

We’ve seen that this issue can crop up for folks when there are too many tasks coming back from Asana, and the vast majority of them are completed, which is what’s making the payload too large.

It looks like this issue is related to how many total tasks you have (including completed tasks). Typically, we handle large numbers of tasks by filtering or pagination, but unfortunately, Asana’s API doesn’t offer much in the way of filtering and we don’t support the type of pagination that they offer. Because of this, the Zap will continue to fail and unfortunately, there’s not much we can do about it. I’m sorry for the bad news!

Our best recommendation is to move any completed tasks in that specific project to another project, if possible. That should keep the number of incomplete tasks low enough for the Zap to function properly. Would that work for you here?

I’m also going ahead and adding your email to a list of folks who are getting affected by this error, so that we can notify you once there are any improvements with this!

Do let me know if you run into further questions here.

So essentially, sounds like the Zapier/Asana integration is just outdated and they haven’t gotten enough requests with people annoyed to fix it yet.

Pretty frustrating because this would be a simple fix if we were using the direct Asana API. Also pretty sure that the Asana/Zapier integration is managed by Asana, and they don’t have much concern at all about updating Zapier.

Definitely a frustrating boat to be in as an end user.

[Phil_Seeman]

@abass

Also pretty sure that the Asana/Zapier integration is managed by Asana

I don’t think this is the case; almost positive it’s managed by Zapier. See When will Asana have a zap "create project from template"!?!?! for a bit more.

[abass]

Ah yes, I made a post asking Asana to take it over a few months ago:

Please Take Over Zapier Integration Development

Zapier told me that if we can convince Asana to take over the integration that would be super helpful and would likely result in more frequent updates and fixes. There are a few bugs in it right now. For example, you can’t create a task with multiple projects tied in the current Zapier configuration. It’s just a bug and tough for Zapier to put all of the resources behind fixing them all. Asana’s team is far larger and would likely do a better job keeping their integration working and bug-free. …

So I guess that Zapier has to get a ton of complaints before they update their integration, sadly

[Phil_Seeman]

Yeah - or Asana can decide to take it over. (They have a few more developer relations resources than they did previously, so one can hope…)

[Finn_Stenberg]

Hi!

I just received the same error message. Did you ever managed to solve it somehow?

Use it to track new projects created in the organization.

[Finn_Stenberg]

Zapier has now turned off the “ZAP” due to the continuous error messages.

Has there been a solution to this matter that I have foreseen?
Any ideas that might help?

[Finn_Stenberg]

Hi!

I have now posted a product feedback for this.

Admin feature? - notification when a project or team is created

We are quite a big organisation and I’m overseeing most of the operations and are also an Asana admin. To be able to track what’s going on and keeping Asana in order, I have set up a Zapier integration that notifies me whenever a project or team is created within the organisation. However lately due to the amount of data we keep in Asana, Zapier no longer is able to work Therefore I suggest an integrated Asana feature for the same! Hope there are more people having this demand and that could v…

[Robert_Gulbahce]

Hi @abass thanks for highlighting this issue with Zapier. Are you aware if the pagination issue is still around. We are doing a big roll out and want to know what to prepare for once we start building lots of tasks within the Asana project.

[abass]

Genuinely not sure, haven’t messed with this in a while. Sorry about that!

[Phil_Seeman]

@Robert_Gulbahce,

There was work done on and improvements made to the Asana Zapier connector back in September. Unfortunately I wasn’t able to find any details on what was changed, so not sure if it involved pagination or not. I’m pretty sure Zapier is in charge of that connector, so you might want to query them on it.

[Robert_Gulbahce]

Thank you @Phil_Seeman and @abass I’ve dug further and read in an update from Zapier that they have resolved the issue. Thank you for your reply here.

[Jennifer_Hetheringto]

This error has just come up for me using Power Automate, so it’s still an issue there as well.

[Cliff]

I’m getting this error as of today. Anybody else? Or any tips on workarounds?

[Andre_Lung]

For me it’s happening in Google Apps Script with the line:
var response = UrlFetchApp.fetch("https://app.asana.com/api/1.0/projects/" + projectGid + "/tasks?opt_fields=completed_at,created_at,custom_fields.enum_value.name, name", getAsanaAuth());

I think google and the UrlFetchApp always handled pagination, so this feels strange. Somewhere deep in my heart I hope it just goes away eventually

[David_Neal]

Hi @Andre_Lung,

I don’t believe fetch will automatically page results for you. If the number of tasks has grown too large to return in a single API call, you can try one of the following.

• Implement a recursive function that loops until all pages have been retrieved. The response from the API includes a next_page object with properties such as offset, path, and uri to assist you in retrieving the next page of results from the API. See the guide on Pagination.
• Filter the tasks returned by the API by using one or more of the get tasks API’s parameters, such as section, modified_since, or completed_since.

Hope this helps!

[bnedev]

I have the same issue with Power Automate. My flow has been running for months without issues and now I get this same error message.

My flow runs on a trigger When a task is created (V2) so pagination is not relevant in here. I wonder as the project grows (has more tasks) for some reason Asana sends larger payload?

Have you found any solution to this? Thanks.