Add the "Internal Exception" Troubleshooting #9231
Conversation
This is to give the Pantheon customers and clients a temporary official documentation for the workaround while this is still being addressed for better error handling/messaging.
| ``` | ||
|
|
||
| To resolve this, create multidev first before pushing the `pantheon.yml` changes. | ||
|
|
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
@rachelwhitton Not sure about SME but @greg-1-anderson might have some context...
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Thanks all! I'll close this PR for now
rachelwhitton
added
Process: Needs SME
Summary
Pantheon YML Troubleshooting - This is to give the Pantheon customers and clients temporary official documentation for the workaround while this is still being addressed for better error handling/messaging.