TaskQueues vs Cloud Tasks std env

[Linus Larsen]

For appengine std env the TaskQueue page in console has been removed, instead you get redirected to the Cloud Task page. However before I can visit that page I need to enable the Cloud Task api for my project.

AFAIK we are not yet forced to swap TaskQueues to CloudTasks, in fact CloudTasks still lacks some features present in TaskQueue (transactional tasks for example), also pricing would be an argument not to use CloudTask.

Anyhow, I don't understand why I need to enable an API that I'm not even sure to use just to be able to run some of my TaskQueues manually in the web console?

Cron page has also been moved to CloudScheduler page, however there I didn't need to enable CloudScheduler api to be able to run crontabs in web console.

/ Linus

   

[Elliott (Cloud Platform Support)]

Hello,

I was able to reproduce the scenario from your description regarding the Cloud Tasks API and the Cloud Scheduler API. You are correct.

I then did some research and found out that the new user interface (UI) uses the Cloud Tasks API. Although the migration to Cloud Tasks is not mandatory right now, the API will need to be enabled in anticipation. This is part of the path to the eventual adoption of Cloud Tasks.

You’ve stated that Cloud Tasks are missing some features that are present in TaskQueue such as transactional tasks and that that pricing would be a point not to use it. This is good feedback and I encourage you to contribute a feature request to describe your ideas.

I hope this did not cause inconvenience on your part and if you have any related questions about this, you may post again.