UPDATE: Thanks to @Shay for asking this question, the issue he encountered is no longer an issue, as we have allowed aliases to work (when relevant) in the Task Queue API.
For posterity here is the original answer below:
Two of the most common mistakes I have seen are:
Forgetting to include the
s~
in your App Engine Project. For example, if your application ID ismy-awesome-app
, then you are callingtq.get(project='my-awesome-app', taskqueue=PULL_QUEUE_NAME...
when you should be calling
tq.get(project='s~my-awesome-app', taskqueue=PULL_QUEUE_NAME...
Forgetting to add the Compute service account to the task queue ACL in
queue.yaml
. To do this, you need to get the service account associated with your project and add it to theacl
:queue: - name: pull-queue mode: pull acl: - writer_email: 123845678986@project.gserviceaccount.com # can do all
and of course this would mean
PULL_QUEUE_NAME = 'pull-queue'
here. Also note,123845678986@project.gserviceaccount.com
should be replaced with the service account for your Compute Engine instance.