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-03-05 UTC."],[[["This API information pertains to first-generation runtimes and is relevant when upgrading to corresponding second-generation runtimes."],["The document outlines limitations when utilizing the local development server (`dev_appserver`) for testing push queues."],["The local development server does not adhere to the `rate` and `bucket-size` queue attributes, resulting in tasks executing near their ETA regardless of rate settings."],["Queue state is not retained across restarts of the development server."]]],[]]
