Troubleshoot the Experience Modernization Agent troubleshooting

Find the symptom, then follow its section. Most problems come from access to the source site, from the accounts that write code and content to your Adobe Experience Manager Edge Delivery Services site, or from a difference between your console workspace and what is saved in Git and in your content source.

Before you reset, discard, replace, or overwrite anything, preserve the affected work. Code and content are recovered separately; see Release, Recover, and Hand Over.

If this page doesn’t solve the problem, request support in the console, or select Get help on the Auto mode pages.

Import Fails import-fails

Keep the error and the exact source URL, and check that the URL opens in a browser. If pages require sign-in, or a capture shows a sign-in page instead of the content, set up protected site authentication. If the source site blocks automated access, see Source Sites with Bot Protection. If the source is reachable, give the agent the error and ask it to fix the import of that page. Retry one affected page before you repeat a batch.

Source Sites with Bot Protection bot-protection

Bot protection in a content delivery network (CDN) or web application firewall (WAF) can block or challenge the agent’s requests to a source site in every workflow: URL discovery, the site catalog, page capture, and import. Typical signs are access-denied errors such as HTTP 403, 429, or 503, URLs missing after discovery, failed pages, or a challenge or verification page captured instead of the page content.

Migrate only sites that you own or are authorized to migrate. Arrange access with the site’s administrator rather than working around the protection:

Check one page, including its images and other assets, before you start a catalog or batch run. After access changes, retry the failed pages, and check captures for challenge or access-denied pages before you accept the content.

Allowlist IP Addresses allowlist-ip-addresses

With your source-site administrator’s approval, allowlist these backend addresses for source extraction:

Allowlisting gives network access only: the source must still be reachable over the internet, and protected pages still need Protected Site Authentication.

A Change Is Missing missing-change

Code and content are saved in different places, so check each one: the console workspace, the uploaded content, the pushed branch, and the previewed page. A reimport overwrites local content changes, so upload or reconcile edits before you import a page again. To compare the console preview with the preview site, see Console Preview Differs from the Site.

Console Preview Differs from the Site preview-differs

The console preview and the preview site render different copies of the content and code, as Know Which Result You Are Viewing explains. Look for one of these causes:

Content Writes Fail write-errors

Code and content use different accounts. Code is pushed with your GitHub connection, or your Cloud Manager connection for other Git hosts. Content is written to Experience Workspace with the Adobe account that you signed in with. A code push can therefore succeed while a content upload fails, or the other way round.

If an upload, pull, or transfer says that your Document Authoring session may have expired, sign in again and retry. The console shows the same message when the session is valid but your Adobe account doesn’t have write access to the site’s content. If it persists, ask the site’s administrator to confirm that your account, with the email address and organization that you use in the console, can write to the site in Experience Workspace. Access to Experience Manager in Adobe Admin Console doesn’t by itself grant write access to a site’s content. If the console says that you are rate limited, wait a minute and retry.

Git Connection Problems git-connection

For what each GitHub app does, see Start from a Repository.

For conflicting changes and protected branches, see Push Code Changes.

Workspace Setup Takes Time or Fails workspace-setup

Preparing a workspace takes up to 10 minutes, the first time you sign in and after a reset. If all workspaces are in use, the console tells you so and starts setting yours up as soon as one is available; you don’t need to retry. If you need it sooner, select Request support. If setup fails, the console offers to retry. If it keeps failing, use the Request support link on the setup screen. If the console says that your account can’t use it, contact your Adobe account team. For a workspace that shows Your workspace is paused, see Open the Experience Modernization Console.

Project Seems Missing missing-workspace

If you belong to several Adobe organizations, the project may be in another organization’s console workspace. Sign out, then sign in with the same account and choose the profile of the organization that you used before. Don’t reset the workspace while you investigate: a reset deletes work that you haven’t pushed. If the project is still missing, request support with the project name and preview URL. Pushed code and uploaded content are safe in your Git repository and content source either way.

Failed to Send Message send-failed

Failed to send message. Please try again. means that the console couldn’t deliver your prompt to the agent. The message doesn’t give the cause, which can be your network connection, an expired sign-in, or a temporary service problem.

If the console instead says that it’s at capacity, see Workspace Setup Takes Time or Fails.

Remove Pages remove-pages

A safeguard in the console stops the agent from deleting files in the project’s content folder, so that migrated content isn’t removed by mistake. Asking the agent to delete pages therefore doesn’t work. Remove them yourself, in each place where they exist:

If pages were imported to the wrong path, import them again to the correct path, check them, and then delete the copies at the wrong path.