That’s great that they’re responsive and that it’s isolated, and thanks for all your work with them and me.
I’m confused. If I do https://app.asana.com/api/1.0/workspaces/2495486071216/users I only get around 30 results.
Is there a chance they’re actually instead using:
because if I do that I get:
"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: https://asana.com/developers/documentation/getting-started/errors"
I think they’re using that endpoint because no matter which workspace I choose in:
it always hangs–I don’t think they’re using the former endpoint. I think they should not be using that latter endpoint (if they are). If they’re using the former endpoint for the gid of the chosen workspace, then I’m not over 1000.
(Regardless of all that, since Assignee is optional according to their form, if they fail when trying to load it, why don’t they just set the input field to a valid “no assignee” value to let the form pass and just ignore it; they don’t need to implement paging to make this work. But really, the proper solution is to use the correct endpoint which is maybe not what they’re doing.)
Hope that makes sense! Maybe there’s a solution here!