Stay organized with collections
Save and categorize content based on your preferences.
This page describes some limitations with using the local development server (dev_appserver) to test push queues in your application.
In most respects, you set up your queues and tasks just as you would to run them in the
App Engine production environment, but there are some differences:
The development server doesn't respect the rate and bucket-size attributes
of your queues. As a result, tasks are executed as close to their ETA as
possible. Setting a rate of 0 doesn't prevent tasks from being executed
automatically.
The development server doesn't preserve queue state across restarts.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[[["\u003cp\u003eThis API information pertains to first-generation runtimes and is relevant when upgrading to corresponding second-generation runtimes.\u003c/p\u003e\n"],["\u003cp\u003eThe document outlines limitations when utilizing the local development server (\u003ccode\u003edev_appserver\u003c/code\u003e) for testing push queues.\u003c/p\u003e\n"],["\u003cp\u003eThe local development server does not adhere to the \u003ccode\u003erate\u003c/code\u003e and \u003ccode\u003ebucket-size\u003c/code\u003e queue attributes, resulting in tasks executing near their ETA regardless of rate settings.\u003c/p\u003e\n"],["\u003cp\u003eQueue state is not retained across restarts of the development server.\u003c/p\u003e\n"]]],[],null,["# Testing Push Queues in the Development Server\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nGo Java PHP Python\n| This API is supported for first-generation runtimes and can be used when [upgrading to corresponding second-generation runtimes](/appengine/docs/standard/\n|\n| /services/access). If you are updating to the App Engine runtime, refer to the [Upgrade to second-generation runtimes]() page to learn about your migration options for legacy bundled services.\n\nThis page describes some limitations with using the [local development server](/appengine/docs/standard/tools/using-local-server) (`dev_appserver`) to test push queues in your application.\nIn most respects, you set up your queues and tasks just as you would to run them in the\nApp Engine production environment, but there are some differences:\n\n- The development server doesn't respect the `rate` and `bucket-size` attributes of your queues. As a result, tasks are executed as close to their ETA as possible. Setting a rate of `0` doesn't prevent tasks from being executed automatically.\n- The development server doesn't preserve queue state across restarts.\n\nFor more detailed information on the options available using the local\ndevelopment server, see\n[Using the local development server](/appengine/docs/standard/tools/local-devserver-command)."]]
