Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add the "Internal Exception" Troubleshooting #9231

Closed
wants to merge 1 commit into from
Closed

Add the "Internal Exception" Troubleshooting #9231

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions source/content/pantheon-yml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -328,6 +328,21 @@ remote: Valid versions are: 1

While our parser will reject a `pantheon.yml` that is invalid, it won't necessarily give you the exact reason the file is invalid. Syntax errors are the most common reason for an invalid `pantheon.yml` file.

### There was an internal error processing the request

The Platform will throw an "internal error" when you try to push a commit that includes a `pantheon.yml` changes to a **_branch without an associated multidev_**. The error message will resemble:

```none
remote: PANTHEON ERROR:
remote:
remote: The specific error returned was: Internal exception
remote:
remote: There was an internal error processing the request
remote:
```

To resolve this, create multidev first before pushing the `pantheon.yml` changes.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could not reproduce this issue on a d10 Integrated Composer performance small site and a vanilla WP sandbox site. In both cases, the push was successful without existing multidevs.

On both test sites, I checked out a new branch locally and made changes to pantheon.yml (upgraded PHP versions), committed, and pushed with the following result:

remote:
remote: PANTHEON NOTICE:
remote:
remote: Skipping code sync, no Multidev environments were found for branch "php8-3".
remote:

@ersonjn can you provide the full error message output for the support issue related to this docs PR? I expect something else caused this internal error and the surrounding output should help identify. Or if you have the ticket number?

@jazzsequence can you recommend an SME for this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rachelwhitton Not sure about SME but @greg-1-anderson might have some context...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about the cause of the reported error. It happens intermittently, and rarely. I think it only happens if the name selected refers to a multidev that used to exist, but no longer does. I don't think that you can reproduce this simply by creating and deleting a multidev; there is something more complex at work.

Since this problem happens only rarely, and the symptoms might also be indicative of a different platform problem, I don't think that we should include this workaround in our public docs.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks all! I'll close this PR for now

### Why can’t I update the PHP version on my Multidev?

The PHP version changes automatically when you modify the `pantheon.yml` file of a site with a pre-existing Multidev. A PHP version change will not appear in a Multidev created after your `pantheon.yml` changes are made. To update your Multidev:
Expand Down
Loading