-
Notifications
You must be signed in to change notification settings - Fork 619
[Docs] EC troubleshoot #7496
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.
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
[Docs] EC troubleshoot #7496
Conversation
Signed-off-by: samina <[email protected]>
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughA new collapsible section was added to the troubleshooting guide, providing instructions for deleting Transactions Cloud. The update explains how to remove associated code and when to delete the entire project. No existing content or logic was changed. Changes
Sequence Diagram(s)No sequence diagram generated as the change is documentation-only. Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7496 +/- ##
=======================================
Coverage 51.92% 51.92%
=======================================
Files 949 949
Lines 64148 64148
Branches 4229 4229
=======================================
Hits 33311 33311
Misses 30731 30731
Partials 106 106
🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
apps/portal/src/app/engine/v3/troubleshoot/page.mdx(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
PR: thirdweb-dev/js#0
File: CLAUDE.md:0-0
Timestamp: 2025-06-30T10:25:29.488Z
Learning: Surface breaking changes prominently in PR descriptions
⏰ Context from checks skipped due to timeout of 90000ms (8)
- GitHub Check: E2E Tests (pnpm, vite)
- GitHub Check: Unit Tests
- GitHub Check: E2E Tests (pnpm, esbuild)
- GitHub Check: Size
- GitHub Check: E2E Tests (pnpm, webpack)
- GitHub Check: Lint Packages
- GitHub Check: Build Packages
- GitHub Check: Analyze (javascript)
| <Details summary="How do I delete Transactions Cloud?"> | ||
|
|
||
| To delete or stop sending requests on Transactions Cloud, you may stop sending requests through your codebase and remove associated code. If you don't want Transactions Cloud and are not using any other features within the same project, you may delete the associated project as well. | ||
|
|
||
| </Details> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Clarify product naming & give concrete deletion steps
The header refers to “Transactions Cloud”, yet the PR description says the doc is for deleting Engine Cloud. If the service was renamed, we risk confusing users.
Additionally, simply telling users to “remove associated code” lacks actionable detail (e.g., which SDK calls / dashboard toggles to disable). A quick bullet-list or link to the “Delete project” UI would make the guidance far more useful.
Example patch:
-<Details summary="How do I delete Transactions Cloud?">
-
-To delete or stop sending requests on Transactions Cloud, you may stop sending requests through your codebase and remove associated code. If you don't want Transactions Cloud and are not using any other features within the same project, you may delete the associated project as well.
-
-</Details>
+<Details summary="How do I delete Engine Cloud?">
+
+If you no longer need Engine Cloud:
+
+1. **Remove SDK calls** – delete any `engine.send(...)` or `thirdwebEngine.*` invocations in your codebase.
+2. **Disable the service** – in the dashboard, go to **Project Settings → Services → Engine Cloud** and toggle it off.
+3. **Delete the project (optional)** – if the project is unused, scroll to **Danger Zone → Delete Project**.
+
+</Details>This resolves the naming discrepancy and provides step-by-step instructions.
Ensure the product name in the summary matches the branding used across the docs/repo. If it really is “Transactions Cloud”, adjust references elsewhere accordingly.
🏁 Script executed:
#!/bin/bash
# Search for occurrences of "Transactions Cloud" versus "Engine Cloud" across the repository
rg "Transactions Cloud" -n
rg "Engine Cloud" -nLength of output: 4986
Maintain “Transactions Cloud” naming & add actionable deletion steps
The header should remain “Transactions Cloud” (v3 docs consistently use this term). Expand the details to give users concrete, step‐by‐step instructions.
apps/portal/src/app/engine/v3/troubleshoot/page.mdx
-<Details summary="How do I delete Transactions Cloud?">
-
-To delete or stop sending requests on Transactions Cloud, you may stop sending requests through your codebase and remove associated code. If you don't want Transactions Cloud and are not using any other features within the same project, you may delete the associated project as well.
-
-</Details>
+<Details summary="How do I delete Transactions Cloud?">
+
+If you no longer need Transactions Cloud:
+
+1. **Remove SDK calls** – delete any `transactions.send(...)` or `thirdweb.transactions.*` invocations in your code.
+2. **Disable the service** – in the dashboard, go to **Project Settings → Services → Transactions Cloud** and toggle it off.
+3. **Delete the project (optional)** – if the project is unused, scroll to **Danger Zone → Delete Project**.
+
+</Details>- Keeps naming aligned with v3 docs
- Provides clear, actionable steps for both code and dashboard cleanup
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <Details summary="How do I delete Transactions Cloud?"> | |
| To delete or stop sending requests on Transactions Cloud, you may stop sending requests through your codebase and remove associated code. If you don't want Transactions Cloud and are not using any other features within the same project, you may delete the associated project as well. | |
| </Details> | |
| <Details summary="How do I delete Transactions Cloud?"> | |
| If you no longer need Transactions Cloud: | |
| 1. **Remove SDK calls** – delete any `transactions.send(...)` or `thirdweb.transactions.*` invocations in your code. | |
| 2. **Disable the service** – in the dashboard, go to **Project Settings → Services → Transactions Cloud** and toggle it off. | |
| 3. **Delete the project (optional)** – if the project is unused, scroll to **Danger Zone → Delete Project**. | |
| </Details> |
🤖 Prompt for AI Agents
In apps/portal/src/app/engine/v3/troubleshoot/page.mdx around lines 12 to 16,
keep the header as "Transactions Cloud" to maintain naming consistency with v3
docs. Expand the content inside the Details tag to include clear, step-by-step
instructions for users on how to delete or stop using Transactions Cloud,
covering both codebase changes (like stopping requests and removing related
code) and dashboard/project cleanup actions. Make sure the instructions are
actionable and easy to follow.
size-limit report 📦
|
| </Details> | ||
| </Details> | ||
|
|
||
| <Details summary="How do I delete Transactions Cloud?"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is more of a FAQ no?
CORE-0000
added article on deletng engine cloud
PR-Codex overview
This PR adds a new section to the
page.mdxfile, providing guidance on how to delete Transactions Cloud. It enhances the documentation by offering clear instructions for users.Detailed summary
Detailssection with the summary "How do I delete Transactions Cloud?"Summary by CodeRabbit