"You do not have access to this pot" error when getting projects for team

English Forum Developers & API
1

Hello,

I am having an issue with getting a team’s projects. I am working on a Python script but I was able to replicate this issue via the API webpage (Get a team's projects) sending a shell request.

This is the response:
“message”: “You do not have access to this pot.”,
“help”: “For more information on API status codes and how to handle them, read the docs on errors: Errors”

This error is triggered by the created_from_template field (and created_from_template.name), which is a roadblock for my project as that’s a required output.
I am not sure if I understand the API correctly so please bear with me, but even if my token does not have access to a particular template, why does that break the entire response? I am perfectly able to get all projects for this team if I remove the field, but that doesn’t help me.
I would also note that I am able to get this data for other teams within my workspace.

Can you please advise?

Thank you,
Alex

2

Apologies for the bump, however this is quite critical to my project and I would like to make sure I haven’t overlooked anything trivial on my end.

3

Does it literally say the word “pot”? That’s not a term I’ve ever heard used related to Asana, so just a bit odd.

Will try to ping someone at Asana on this.

4

@Alex_Franchini, Is there any chance is just an access/permission issue? Can you maybe not reach that template in the UI (but can reach others in the UI, and those don’t throw errors)?

@Phil_Seeman, “pot” has been used in Asana front-end code, at least, for a very long time. I don’t know that I ever knew the exact origin/meaning but I’m pretty clear it refers to either a work object itself or the unique id portion of the URL of that work object.

Thanks,

Larry

5

Hi @lpb @Phil_Seeman ,

Thanks for your responses, appreciate it!
I have also seen the “you do not have access to this project_recipe” error message, besides the “pot” one.
For context, I am trying to pull project information across a fairly large list of teams which makes it hard to troubleshoot exactly which items we may not have access to.

My next step today was to try and get a full list of projects (without pulling the created_from_template field) and then compare that list with the more limited subset to try and get to whatever is missing from the UI.
I guess it would have been helpful if the API still returned a valid response except for something mentioning the permissions issue in the relevant field.

Thanks,
Alex

1 Like
6

I heard from one of my Asana contacts that “pot” is an internal term they use which shouldn’t be showing in any customer-facing messages, so they may fix that one.

In terms of the core issue, I misunderstood your initial post, sorry; I concur with @lpb that it’s probably failing when you don’t have permission to the template.

I’m not sure having the rest of the data be returned, just not the one field, if you don’t have access to the template, because that field would then likely be null which would be deceiving since it would seem like the project was not created from a template when it actually was.

3 Likes