Two users working on the same organization do not see changes made by each other until those changes are executed and the other user refreshes their display. Unexecuted persisted changes may conflict with executed changes. If there are conflicts, they are reported at execution time, or in cases where data is refreshed due to sign out/ sign in or browser refresh, at data reload time.
Last updated on
Jul 1, 2024
- Adobe Enterprise & Teams: Administration guide
- Plan your deployment
- Basic concepts
- Deployment Guides
- Deploy Creative Cloud for education
- Deployment home
- K-12 Onboarding Wizard
- Simple setup
- Syncing Users
- Roster Sync K-12 (US)
- Key licensing concepts
- Deployment options
- Quick tips
- Approve Adobe apps in Google Admin Console
- Enable Adobe Express in Google Classroom
- Integration with Canvas LMS
- Integration with Blackboard Learn
- Configuring SSO for District Portals and LMSs
- Add users through Roster Sync
- Kivuto FAQ
- Primary and Secondary institution eligibility guidelines
- Set up your organization
- Identity types | Overview
- Set up identity | Overview
- Set up organization with Enterprise ID
- Setup Azure AD federation and sync
- Set up Google Federation and sync
- Set up organization with Microsoft ADFS
- Set up organization for District Portals and LMS
- Set up organization with other Identity providers
- SSO common questions and troubleshooting
- Manage your organization setup
- Manage users
- Overview
- Administrative roles
- User management strategies
- Assign licenses to a Teams user
- Add users with matching email domains
- Change user's identity type
- Manage user groups
- Manage directory users
- Manage developers
- Migrate existing users to the Adobe Admin Console
- Migrate user management to the Adobe Admin Console
- Overview
- Manage products and entitlements
- Manage products and product profiles
- Manage products
- Buy products and licenses
- Manage product profiles for enterprise users
- Manage automatic assignment rules
- Entitle users to train Firefly custom models
- Review product requests
- Manage self-service policies
- Manage app integrations
- Manage product permissions in the Admin Console
- Enable/disable services for a product profile
- Single App | Creative Cloud for enterprise
- Optional services
- Manage Shared Device licenses
- Manage products and product profiles
- Get started with Global Admin Console
- Adopt global administration
- Select your organization
- Manage organization hierarchy
- Manage product profiles
- Manage administrators
- Manage user groups
- Update organization policies
- Manage policy templates
- Allocate products to child organizations
- Execute pending jobs
- Explore insights
- Export or import organization structure
- Manage storage and assets
- Storage
- Asset migration
- Reclaim assets from a user
- Student asset migration | EDU only
- Manage services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
- Adobe Acrobat Sign
- Creative Cloud for enterprise - free membership
- Deploy apps and updates
- Overview
- Create packages
- Customize packages
- Deploy Packages
- Manage updates
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Troubleshoot
- Manage your Teams account
- Renewals
- Manage contracts
- Reports & logs
- Get help
Changes in the Global Admin Console are done in two phases, making changes to the organizations or allocating products as needed, then reviewing and executing these changes. Learn how you can execute the pending changes.
To ensure that all changes made within the Global Admin Console are implemented and take effect, navigate to the Job Execution tab and proceed with executing them.
You can sign out and back in or even refresh the page without losing edits. Unexecuted changes are discarded after 30 days. However, pending changes are cleared if you close the browser tab or window.
As a global administrator, you can review the list of changes and initiate the execution, or continue to make changes. To execute the changes, do the following:
-
Sign in to the Global Admin Console.
-
Navigate to the Job Execution tab. Review the pending changes, if any, and select Submit Changes to execute them.
The job starts executing, and the status appears as pending until the execution is complete. Adobe recommends having only one job in execution at a time. If an error occurs while executing a job, changes not successfully applied must be reentered.
If an allocation takes over 12 hours to process, the job is marked as failed and any subsequent pending tasks are not executed.
Cancel a running job
To cancel a running job, select Cancel Running Job in the Job Execution tab.
Canceling a running job stops the job at the end of the current step. It does not stop the job immediately in the middle of a step. Some steps may take minutes or hours to complete, so a job may be in the canceling state for some time.
View job history
To view the jobs executed in the past 30 days, do the following:
-
Sign in to the Global Admin Console. In the Job Execution tab, scroll to the bottom of the page.
-
Select Recent Jobs.
- Job commands are listed as they were when they were submitted. Subsequent renames or deletions to not affect display of commands.
- Errors and warnings are displayed with each command.
Adobe MAX
The Creativity Conference
Oct 14–16 Miami Beach and online
Adobe MAX
The Creativity Conference
Oct 14–16 Miami Beach and online