Repository navigation
[docs-agent] Remove alchemy.com/support links - #1727
Merged
Merged
Conversation
Swaps all content references to the legacy alchemy.com/support knowledge base: * Contact-support cases (snapshot deprecations, faucets, clankermon/tea deprecation notices, prices FAQ, OP Mainnet 429 error message) now point at support@alchemy.com via mailto links. * Reference-article cases (wallet FAQ answers for replacement-underpriced + UO retries, wallet API error pages for AA23/AA25/replacement-underpriced) now point at https://support.alchemy.com/ (new Pylon-powered knowledge base). * /discuss/:path* redirect destination updated from www.alchemy.com/support to support.alchemy.com/. Refs Slack thread C03306R8XTL/1793037771.667969 Requested-by: @dslovinsky
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
🔗 Preview Mode
|
…wallet-apis-errors Per dslovinsky review feedback on PR #1727: linking to the support homepage from text that explicitly references 'these recommendations' doesn't make sense when there is no equivalent page. Removes the trailing 'Follow [these recommendations](https://support.alchemy.com/).' sentence from the Replacement underpriced, AA23, and AA25 <Info> callouts entirely. Refs Slack thread C03306R8XTL/1793037771.667969 Requested-by: @dslovinsky
…allets FAQ Per dslovinsky review feedback on PR #1727: same reasoning as commit 0e55fb8 (links to the KB homepage from text that explicitly references 'recommendations' or 'this guide' are misleading when no equivalent page exists). Removes the dangling 'Please follow recommendations [here](...)' sentence from the Replacement underpriced Accordion answer and the 'Please follow [this](...) guide for best practices' sentence from the FailedToFindTransactionError Accordion answer. Refs Slack thread C03306R8XTL/1793037771.667969 Requested-by: @dslovinsky
vahnag
approved these changes
Oct 27, 2026
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
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.
Summary
Removes all content references to the legacy
alchemy.com/supportknowledge base, per request to retire that domain.Treatment follows the two rules from the ask:
support@alchemy.com(asmailto:links). Covers the Avalanche/Aptos snapshot deprecation notices, the extra-faucet-tokens callout, the Clankermon and Tea deprecation notices, the Prices API "need another token?" FAQ, and the OP Mainnet 429 error-message cell.https://support.alchemy.com/(new Pylon-powered knowledge base). Covers the wallet FAQ answers for replacement-underpriced + UO retries, and the wallet API error reference pages for AA23 / AA25 / replacement-underpriced./discuss/:path*destination incontent/redirects.ymlis swapped fromwww.alchemy.com/support→support.alchemy.com/since it isn't a "contact support" context.Files changed
content/redirects.yml/discuss/*destination →support.alchemy.com/content/wallets/pages/resources/faqs.mdxsupport.alchemy.com/content/wallets/pages/troubleshooting/wallet-apis-errors.mdxsupport.alchemy.com/content/tutorials/snapshots/avalanche.mdxsupport@alchemy.comcontent/tutorials/snapshots/aptos.mdxsupport@alchemy.comcontent/tutorials/getting-started/faucets.mdxsupport@alchemy.comcontent/api-reference/clankermon/clankermon-deprecation-notice.mdxsupport@alchemy.comcontent/api-reference/op-mainnet/op-mainnet-api-faq/op-mainnet-error-codes.mdx<https://alchemy.com/support>tosupport@alchemy.comcontent/api-reference/data/prices-api/prices-api-faq.mdxsupport@alchemy.comcontent/api-reference/tea/tea-deprecation-notice.mdxsupport@alchemy.comNotes for reviewer
how-to-fix-replacement-underpriced-errors,how-to-resolve-entrypoint-aaxx-errors,best-practice-guide-on-how-to-implement-user-operation-retries) do not have direct equivalents on the new help center yet. The new KB uses numerical article IDs under/articles/<id>-<slug>and its Wallet APIs collection currently only lists 5 unrelated articles. Per the ask ("For all other cases use support.alchemy.com"), these links now point at the roothttps://support.alchemy.com/so users land on the knowledge base and can navigate. Happy to swap in specific article URLs if the equivalents are migrated.alchemy.com/supportin that message; worth confirming with the Node team if that string is still live verbatim.Requested by
@dslovinsky (via Slack thread)