CloudTasks Queue (HTTP Tasks) break when disabling AppEngine

[Micah Thomas]

Hello,

I am having trouble with Cloud Tasks (HTTP Request Tasks) breaking when I disable my app-engine application. For the time being I've re-enabled the app-engine application to get the cloud tasks queue to keep working. I thought Cloud Tasks was a separate project, and does not depend on appengine.

Not sure who I should be talking to, if this is not the right group/place.

[jstsetinin]

Hello,

Thak you for your question.

According to our documentation "You must have an enabled App Engine application in your project to run your queue." [1]

It is not possible to make it work without Appengine.

[1] https://cloud.google.com/tasks/docs/quickstart-appengine

[Micah Thomas]

Thanks for pointing that out.

I didn't get that impression from anywhere else, and it was confusing that cloud tasks have it's own page in google cloud if it depends on appengine.

Anyway, I'll probably look into another system, and just keep the appengine app running till I migrate our queues over to something else.

[wesley c]

There are 2 different types of (push) tasks that Cloud Tasks can handle, and it depends on *where* the tasks are handled. These are called "targets," and you can have App Engine targets, meaning the tasks run on and are handled by App Engine, or generic HTTP targets, meaning the tasks are hosted and are handled elsewhere, say a VM, Cloud Functions, etc. You can read more about both types in this official docs page.

Focusing more specifically on your question, if your target tasks are hosted on App Engine, then you project/app should *not* be disabled, but if it is a standard HTTP target, you don't need an App Engine app for *that* case. Hope this helps!

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f09a677a-7f5e-424f-bcfb-5ddd5b7ead78n%40googlegroups.com.

--

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
    wesley chun :: @wescpy :: Software Architect & Engineer
    Developer Advocate at Google Cloud by day; at night...

    Python training & consulting : http://CyberwebConsulting.com
    "Core Python" books : http://CorePython.com
    Python blog: http://wescpy.blogspot.com

[Micah Thomas]

Wesley,

Our application uses HTTP handlers that are running in kubernetes on the same project, we don't use any appengine targets.

The issue is that even w/o any handlers running in appengine, if I disable the appengine project, cloud tasks stop working.

I now see that the official docs page has a note: The appengine project must stay enabled for queues to function.

It would be better for user experience if this info is shown when you go to disable the appengine project so that a user is not surprised when the queues stop working.

[wesley c]

Thanks for the feedback... I see you're referring to the NOTE sidebar here, correct? Is your request to have a similar note placed on the Cloud Console page to disable their App Engine apps warning users it will also disable their Task Queues, regardless of where the task handlers are (GAE or not)?

If so, go to that page in the docs, in the upper right corner, click the "Send Feedback" button and use the tool to submit a screenshot of that NOTE and let us know this warning should also appear on that Cloud Console page. This will give weight to any bug filed (when customers experience issues like this).

I think the reason you have to have an enabled App Engine "app" (in the console even if you don't actually have any code running on App Engine) is that Cloud Tasks originated from App Engine, and they haven't fully migrated it away from GAE yet.

Thanks,

--Wesley