Concurrency considerations
Stay organized with collections
Save and categorize content based on your preferences.
You should not use the Developer Console and the Publishing API concurrently
to update applications because of the potential for unintended side effects.
The following is a list of some example scenarios that illustrate the
expected behavior if you decide to use the Developer Console and the
Publishing API concurrently to update your application, or use multiple
concurrent Publishing API clients.
Committing an edit while changes are ready to send for review in the Developer Console
Committing an edit will send all changes for review, including changes ready
to send for review in the Developer Console.
For example, assume you have changes ready to send for review in the Developer
Console. If you create, edit, and then commit an edit using the API, the commit
action sends all changes to your application for review, including those made
through the Developer Console.
Making changes in the Developer Console invalidates active edits
If you have an active edit made using the API, and you then update your
application using the Developer Console, the edit is invalidated. You need to
create a new edit to update your application through the API.
Creating a new edit invalidates any active edits for the same application by the same user
Creating a new edit for an application invalidates any active edits for that
application created by the same user. Each API user can have only one active
edit per application.
Multiple users can have active edits for the same application
If two users create edits for the same application, both edits are
active for both users until one is committed. The first committed edit
invalidates all other edits for that application.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-08-21 UTC.
[null,null,["Last updated 2024-08-21 UTC."],[[["\u003cp\u003eAvoid using the Developer Console and the Publishing API simultaneously for application updates due to potential conflicts and unexpected outcomes.\u003c/p\u003e\n"],["\u003cp\u003eConcurrent edits, whether through the Developer Console or multiple Publishing API clients, can lead to one edit overriding others, requiring careful management of updates.\u003c/p\u003e\n"],["\u003cp\u003eInitiating a commit action using the API will send all pending changes for review, including those staged in the Developer Console.\u003c/p\u003e\n"],["\u003cp\u003eMaking changes in the Developer Console while an API edit is active will invalidate the API edit, necessitating a new edit for API-based updates.\u003c/p\u003e\n"],["\u003cp\u003eOnly one active edit per application is allowed per API user; creating a new edit invalidates any existing active edits by the same user for that application.\u003c/p\u003e\n"]]],["Using the Developer Console and Publishing API simultaneously can cause issues. Committing an API edit sends all changes for review, even those made in the Developer Console. Developer Console changes invalidate active API edits, requiring a new edit to be made. A new edit from one user invalidates their other active edits. Multiple users can have active edits, but the first commit invalidates the others. Concurrent use of these methods can result in unintended changes being published.\n"],null,["# Concurrency considerations\n\nYou should not use the Developer Console and the Publishing API concurrently\nto update applications because of the potential for unintended side effects.\n\nThe following is a list of some example scenarios that illustrate the\nexpected behavior if you decide to use the Developer Console and the\nPublishing API concurrently to update your application, or use multiple\nconcurrent Publishing API clients.\n\nCommitting an edit while changes are ready to send for review in the Developer Console\n--------------------------------------------------------------------------------------\n\nCommitting an edit will send all changes for review, including changes ready\nto send for review in the Developer Console.\nFor example, assume you have changes ready to send for review in the Developer\nConsole. If you create, edit, and then commit an edit using the API, the commit\naction sends all changes to your application for review, including those made\nthrough the Developer Console.\n\nMaking changes in the Developer Console invalidates active edits\n----------------------------------------------------------------\n\nIf you have an active edit made using the API, and you then update your\napplication using the Developer Console, the edit is invalidated. You need to\ncreate a new edit to update your application through the API.\n\nCreating a new edit invalidates any active edits for the same application by the same user\n------------------------------------------------------------------------------------------\n\nCreating a new edit for an application invalidates any active edits for that\napplication created by the same user. Each API user can have only one active\nedit per application.\n\nMultiple users can have active edits for the same application\n-------------------------------------------------------------\n\nIf two users create edits for the same application, both edits are\nactive for both users until one is committed. The first committed edit\ninvalidates all other edits for that application."]]