Skip unmigratable orgs in the provider service split boot migration#1404
Merged
Conversation
…udly The boot-rail service split threw out of planMigration when a monolith config had no stored specHash, which failed the whole data-migration run and left the daemon wedged on startup with only 'Unknown error' on stderr (#1403). Route that throw through the existing per-org hardError path so the org is skipped, warned about, and retried on a later run, and warn about skipped orgs even when no org is migratable. A fatal CLI failure now exits the process instead of parking it with the port unbound, so the desktop shows the crash screen instead of an infinite 'Starting executor'. CLI error rendering walks the cause chain so wrapper errors print the underlying message instead of 'Unknown error'.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | ebabfb8 | Commit Preview URL Branch Preview URL |
Jul 11 2026, 10:11 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | ebabfb8 | Jul 11 2026, 10:12 AM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
This was referenced Jul 12, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The service split migration failed the whole run when one org's Google or Microsoft integration had no stored specHash, which blocked server startup after updating (#1403, #1407). Such orgs are now skipped with a warning and retried on a later run, and the other fixes make a boot failure visible: the daemon exits instead of hanging, and the CLI prints the underlying error instead of "Unknown error".
Fixes #1403
Fixes #1407