Skip to content

[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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

[Docs] EC troubleshoot #7496

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion apps/portal/src/app/engine/v3/troubleshoot/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,10 @@ import { Details } from "@doc";
Ensure that Account Abstraction is enabled for your project by navigating to Project Settings > Enabled Services > Account Abstraction.

If disabled, toggle on Account Abstraction and try the transaction again.
</Details>
</Details>

<Details summary="How do I delete Transactions Cloud?">
Copy link
Member

@joaquim-verges joaquim-verges Jul 2, 2025

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?


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>
Comment on lines +12 to +16
Copy link
Contributor

@coderabbitai coderabbitai bot Jul 1, 2025

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" -n

Length 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.

Suggested change
<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.

Loading