#97 Add handle flow btn action - #100
Merged
Merged
Conversation
… into feat/#97_add_btn_action
… into feat/#97_add_btn_action
sung17
pushed a commit
that referenced
this pull request
Jul 21, 2026
…cebook error on messenger connect - create the oauth callback workspace directly instead of via the dedupe-lock helper, removing lib/oauth-workspace.ts - rethrow SdkException as-is in messenger select-page action so Facebook Graph API errors (e.g. persistent menu #100) show their real message instead of a generic "Failed to connect Facebook page" Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
sung17
added a commit
that referenced
this pull request
Jul 21, 2026
…cebook error on messenger connect (#792) - create the oauth callback workspace directly instead of via the dedupe-lock helper, removing lib/oauth-workspace.ts - rethrow SdkException as-is in messenger select-page action so Facebook Graph API errors (e.g. persistent menu #100) show their real message instead of a generic "Failed to connect Facebook page" Co-authored-by: Deathgiver <anonymous@users.noreply.github.com> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Ibraheem-Aoor
added a commit
to Ibraheem-Aoor/ersal-chatbotx
that referenced
this pull request
Aug 19, 2026
The upstream sync changed the four SKIP_WABA_* flags from error-recovery guards (try the call, catch and skip if flag is set) to early-return guards (skip unconditionally if flag is set). This broke non-BSP self-hosted deployments where addSystemUser fails with (ChatbotXIO#100) Param user does not accept global user IDs. Restored pre-sync pattern: each BSP-only call is always attempted; if it fails AND the corresponding SKIP_WABA_* flag is true, the error is logged at warn level (with err + wabaId context) and swallowed so the connect flow can continue. Also restored specific Facebook error subcode handling in shareCreditLine (1752244 = same business, 1752294 = invoicing policy) that was replaced with a catch-all swallow. Flags: SKIP_WABA_USER_ASSIGNMENT, SKIP_WABA_CREDIT_SHARING, SKIP_WABA_PHONE_REGISTRATION, SKIP_WABA_WEBHOOK_SUBSCRIBE. FORK PATCH ChatbotXIO#17 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016YPsX87Wg1pPUeUjzAUyhZ
hoangle398
added a commit
that referenced
this pull request
Sep 6, 2026
…ror text Every Meta integration threw away half of each Graph failure: `code` and `error_subcode` had nowhere to go (`ErrorLog` has no columns for them), and the developer-facing `message` was discarded whenever `error_user_msg` was present. `formatGraphError` in `@chatbotx.io/utils` composes all four into the one `text` column the error-log table, the inbox failed-message tooltip and the app logger already read, and replaces the per-integration `pickErrorMessage` copies. Meta already opens most Graph messages with its own `(#100) `, so that copy is stripped rather than printed twice. `channelErrorMessage` now skips an `originError` detail the composed message already contains, for the same reason.
hoangle398
added a commit
that referenced
this pull request
Sep 6, 2026
…ror text (#1095) Every Meta integration threw away half of each Graph failure: `code` and `error_subcode` had nowhere to go (`ErrorLog` has no columns for them), and the developer-facing `message` was discarded whenever `error_user_msg` was present. `formatGraphError` in `@chatbotx.io/utils` composes all four into the one `text` column the error-log table, the inbox failed-message tooltip and the app logger already read, and replaces the per-integration `pickErrorMessage` copies. Meta already opens most Graph messages with its own `(#100) `, so that copy is stripped rather than printed twice. `channelErrorMessage` now skips an `originError` detail the composed message already contains, for the same reason.
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
3 participants
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.
No description provided.