# EDU / Teams Commonly Asked

This guide is designed to help TD-Teams and TD-EDU users deliver the best experience for sessions, classes, and training events. It covers onboarding, key links, do’s and don’ts, setting up workflows, and common issues to ensure smooth operation.

#### **ThinkDiffusion Self-Onboarding & Pricing Links:** <a href="#thinkdiffusion-self-onboarding-pricing-links" id="thinkdiffusion-self-onboarding-pricing-links"></a>

**For TD-EDU**

* Onboarding Link:[ Set up your TD-EDU Account](https://learn.thinkdiffusion.com/your-td-edu-account/)
* Pricing Link:[ View TD-EDU Pricing](https://www.thinkdiffusion.com/edu#teams)

**For TD-Teams**

* Onboarding Link:[ Set up your TD-Teams Account](https://learn.thinkdiffusion.com/your-td-teams-account/)
* Pricing Link:[ View TD-Teams Pricing](https://www.thinkdiffusion.com/teams#teams)

***

#### **Ensuring Sufficient Funds for Large Classes** <a href="#ensuring-sufficient-funds-for-large-classes" id="ensuring-sufficient-funds-for-large-classes"></a>

If you’re planning to run a large class with, say, **50 students**, make sure to **add sufficient funds to your team account** so that all **50 students have enough credits to launch machines** without interruptions.

**Here’s why this is important:**

* **When a student launches a machine**, the system **pre-debits the funds** from your total team balance to secure enough resources for the machine's runtime.
* If your team balance **doesn’t have enough funds**, students will face issues launching their machines — even if they haven’t consumed their full usage yet.
* For example, if each student requires **$10 worth of credits** to launch a machine, you’ll need at least **$500 pre-loaded** to ensure everyone can start simultaneously.

**To avoid this, you can:**

1. **Pre-load sufficient funds** in your account before class starts.
2. Monitor usage under **Manage Teams > Set Members Limit** to ensure fair usage.
3. If a student runs into credit issues, you can **manually increase their limit** or add more funds during the class.

***

#### **Setup Credit Spend for Each Student:** <a href="#setup-credit-spend-for-each-student" id="setup-credit-spend-for-each-student"></a>

To prevent abuse or accidental overuse, you can set individual monthly usage limits for each student or workspace member.

If this setting is **OFF**, users will have unrestricted access to the total credits available in your account.

**To set limits:**

In your Team Members section, click "*Set Member Limits*"

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcIn2vKEAq7eDNnzrCauu_v7BGfBnXc-oNNl_xWChoxsP7-H98i-a0cGzkz-g9LzTXhgFe7yn4L-mdU6cZddsNpB8d5imwCv5JWhtRtySF3kYs_puEThWJ33vfcBqFMy3Z0pgwL?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="197" width="624"><figcaption></figcaption></figure>

Toggle the setting to "On" and you can set limits individually or set a standard amount for everyone by clicking the checkboxes for the corresponding students.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXftu_ZJVV-vAKba7UIc2JFCdqWrgybSQFC4SqhfrY1wuRUaMIrHEdFahDDEbb5EYU7qOXHvU7T7MNUnU9-nzAtHnCNSc7eqwpAydad9L0VrMmwaIV-1H_aP3vi1UkFuF_sfDwCx5g?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="386" width="751"><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXc8B_9gl5VNmrOPg56YPSKtBNDFHui4V6WmFDTityuPbeBt2y49ZbUcofwCy170KICVXKGRIO01rx4fzFdvkXkerX3tnzFba8wKb3vkWJDgO5uaGSpmmgX7pqhxo0ZEBCzMmDbnsw?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="385" width="624"><figcaption></figcaption></figure>

You can set the limit one by one for each student.

For convenience, you can apply the same monthly limit to all selected users using the **Monthly Limit Amount** setting.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdYSIqMtUeEIY6Nmx_lP5DfzFOURqluA_nsy6dknKEKCTKOxkiupm7mK9C66zoTEHSwzEKXwattFcAJEqTnLXZHKK_TVzEvVcwYwSdOLJ_hVprW5hmREqyB7f_gXG9ei9bzTZeI6w?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="233" width="616"><figcaption></figcaption></figure>

***

**Setting Up for a Smooth Class: Best Practices & Support**

**1. Pre-Prepare Workflows in Advance**

To ensure a seamless experience for your students, set up your workflows at least a week before your class. Instructors are often busy with last-minute logistics, and the more workflows you have, the more time you'll need to configure them properly on ThinkDiffusion. Some workflows may be incompatible with others or become outdated, so early preparation helps avoid disruptions. We highly recommend a quick **20–30 min pre-test** with our **TD-Support team**.

**Pre-Preparation Checklist:**

* Install any custom nodes required for your workflows.
* Install all necessary models.
* If a custom node or model isn’t working as expected, contact TD Support immediately via your assigned support channel, i.e **Discord**.

***

**2. Get Your Students Logged In Before the Class**

To avoid delays during the session, ensure all your students have successfully logged into **ThinkDiffusion** ahead of time. This helps prevent any technical hiccups during the class.

**Important Note:**&#x57;e do **not** automatically notify individuals you add to your account to prevent issues like mistyped email addresses causing spam or security risks.

* Once you’ve added your team members, you’ll need to send them a personal email with one of the **PDF instructions** provided below to guide them through the login process. Once they sign up, they’ll automatically gain access to your workspace.
* Additionally, please ensure your **workspace has sufficient funds loaded** to allow each student’s machine to launch seamlessly. Running out of credits mid-session can disrupt the learning experience.

[***PDF for school accounts running on Google email systems***](https://learn.thinkdiffusion.com/content/files/2025/01/ThinkDiffusion-SignUp-EDU-2024-GoogleSystem.pdf)

[***PDF for school accounts running on NON-Google email systems***](https://learn.thinkdiffusion.com/content/files/2025/01/ThinkDiffusion-SignUp-EDU-2024-NonGoogle.pdf)

***

&#x20;**3. Leverage TD Support**

Stay in close communication with the TD Support team throughout your setup process and during the class. Your onboarding should include access to a dedicated Discord chat for quick assistance.

***

**4. Notify TD for Scheduled Events**

For scheduled training sessions or classes, inform the TD team at least one day in advance. This allows us to:

* Ensure machine availability for your session.
* Optimize file system performance for multi-user workflows.
* Arrange high-performance compute machines and pre-warm them for instant launch.

***

**5. On-Demand Priority Support**

If you need real-time technical support during a session, coordinate with your TD advisor to have a dedicated support team available. This ensures any unexpected issues can be resolved immediately.

By following these steps, you'll create a smoother experience for both yourself and your students while maximizing the performance of ThinkDiffusion.

***

#### **🚫 Don’ts (Follow These for a Smoother Experience)** <a href="#f0-9f-9a-ab-don-e2-80-99ts-follow-these-for-a-smoother-experience" id="f0-9f-9a-ab-don-e2-80-99ts-follow-these-for-a-smoother-experience"></a>

When working on ThinkDiffusion machines, keep in mind that setting up the environment is slightly different from a local PC. To avoid issues, follow these guidelines:

**ComfyUI Manager**

All TD machines come with **ComfyUI Manager pre-installed** - there’s no need to reinstall it. Doing so can cause machine failures. Since ThinkDiffusion runs in a cloud environment and users don’t have CLI access, we preload the manager to ensure stability.

**Adblocker Issues**

Using an ad blocker **can interfere with system requests**, leading to frequent disconnects and errors. If you experience connection issues, try **disabling your ad blocker**.

**Avoid Unnecessary Custom Node Installations**

Each installed node **adds to your launch time**. If you have **over 30 nodes**, your machine may take **5+ minutes to start** or even fail. Remove any **unused or outdated custom nodes** to keep things running smoothly.

**Running Advanced Workflows on Lower-End Machines:**

**Some workflows (e.g., Flux, Hunyuan, LTX, Flux Lora, WAN, SkyReels, or other complex video workflows)** require substantial **GPU resources** and may fail with **Out-of-Memory (OOM)** errors if you're not using a sufficiently high-end machine. For these workflows, use an **Ultra Machine** to ensure adequate VRAM and performance.

**Uploading Large Files (Over 2GB)**

If you’re on a **Workspace or Team account**, use the **24/7 file browser** for files over 2GB. This lets you manage files **without launching a machine**, saving credits and reducing downtime.

Following these best practices will help you get the most out of ThinkDiffusion while avoiding unnecessary disruptions.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcZ7KQKfuw1OvS88ltWLLXhpdi9UTET8ZXSyZ5Q3l7LKbD_-WkJ9IRm4n6bsWkRiGfUBZ7OAqW2dYBSYaC54C8aLR3MdnLG3lYa_o6j4qnaNG7zm1np-cbUPJamIrmy5W_J8JSbPA?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="65" width="387"><figcaption></figcaption></figure>

#### **Support for Newer Workflows** <a href="#support-for-newer-workflows" id="support-for-newer-workflows"></a>

ThinkDiffusion offers multiple versions of each app to ensure compatibility with different workflows, custom nodes, and models. These versions vary in stability and feature support, giving users flexibility based on their needs.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfp1h02PcIQDGWDMuKMVWRrZDC1kTKnqVkwZhQE2gJ8QBSyabW9O3DeU_llRoMZlc9K2Q6nePYNulJJBMvMCcZvPG2dCemgK48vuWxqALmUsWIsEef8dLmsmtKaeJoijvlEe-9z?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="352" width="591"><figcaption></figcaption></figure>

**Available Versions on ThinkDiffusion:**

* **Beta:** The latest version, often based on the most recent commit from the official repo. Supports the newest custom nodes, workflows, and models but may have some instability.
* **Current:** The stable release, typically two weeks to a few months old. Recommended for users who want a balance of stability and newer features.
* **Previous:** A stable version, usually older than four months. Best for workflows that rely on older models or legacy custom nodes.

Each version comes with supporting notes to help you choose the right one for your workflow.

***

#### **Common Issues** <a href="#common-issues" id="common-issues"></a>

**Machine Failed to Launch:**&#x20;

There can be multiple reasons for launch failures.

**Import failed on custom node**

* Check logs for the recently failed machine using the 24x7 file browser.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeuVy9apAR9AokA6Jc3gnItPlEIA_zgQ4GJSZvGP80Vth87HtoFl7RwHfvV7JwS4uH3GtShxorUYRr04whu3xGFDS4kHwnPbcPA4cMCNP3FQ7DUQXFwoIfJXQQchMOJgAwVCCmP?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="93" width="440"><figcaption></figcaption></figure>

* Navigate to ***comfyui/logs*** and open the latest failed machine log file.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXflmGvi1r4tPKB9Jbp9puFw_OZC5-lbhJEWwNhZNpJG8kOAF9QovCJtyrxGFBsrjavcwPpkn0DQtWA7peJj7UM4492X8Fe0yVjHPaAyLyIw4J4bsWxhJFOmJPXS8lOmHVG54-dn?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="160" width="503"><figcaption></figcaption></figure>

* Look for errors related to custom nodes or "Import Failed."

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeUc9-Y14M2npVfDGN1r20v6-AvdESB23pk-JigehokkDk24yepXtYDW5ik8TMPUO7ZvZR6RC6q4Zhuwtbaq-R0Nzze9kjR2JDIU9z6uZGz-r_dg33jh3mP5vZFNBD6JP0EgNlo?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="80" width="536"><figcaption></figcaption></figure>

* Remove the failing custom nodes from ***comfyui/custom\_nodes*** and restart your session by launching a new machine.

***

**Machine Took More Than 7 Minutes to Launch and Failed Without Errors in Logs:**

* If no errors are found in the logs but the machine failed on launch, the issue could be slow loading.
* If you have more than 50 custom nodes, loading all nodes can be time-consuming.
* In ThinkDiffusion, any launch exceeding **10 minutes** is marked as failed.
  * **Solution:** *Go to **comfyui/custom\_nodes** and remove unnecessary custom nodes.*

***

**Machine failed for unknown reason**

* If neither of the above solutions work, you can reset your ComfyUI or A1111 environment from the **Profile Menu**.
* Click on **Profile** > Locate **Reset to Defaults** > Click on ***Comfy/A1111*****&#x20;Reset**.
* This will clean only custom nodes/extensions while keeping your models and output files intact.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfik5DTwmOvsfKPC3itenKpBnC4CBgCDjv7vhGay0987-ZhNFlV9d2ucjb0yBp7Q4POTsxCeQXm5lenVEZVb6wRk75T8HCPr2VLFVbUkV74sx6ao_FLjkbZDgNN1_ZyE9cuHXDgPA?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="260" width="172"><figcaption></figcaption></figure>

***

**File Browser Not Working:** There can be multiple reasons for file browser failures.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfCrH2TmceSoPhyXe3IupUaLtCRE-oFXta1yjQeQ30DyrUt4amYbqjeASLp37vGCyrEALNloAsJGWPYkS_svT8kcKUrBV8MJ-Tr8c8Hesg20afMNpRgFm46PxGUkPfSunJ83zcvhQ?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="376" width="255"><figcaption></figcaption></figure>

***

**Machine is in an Out-of-Memory (OOM) State**

* Some workflows may consume excessive memory, causing the machine to crash and making the file browser unresponsive.
* **Solution:** Upgrade to a higher-tier machine like **ULTRA** to run your workflow.

***

**File Browser Still Not Working After Relaunch**

* This can be due to a **dependency conflict** caused by a custom node.
* Example: Some older custom nodes may require outdated dependencies (e.g., typing package), leading to file browser failure.

***If the issue persists, contact Support (Discord) for further assistance.***

***

**Custom Node Import Failed**

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd1oyCd8_Wb3OV7shFbvqvUyOJ6OfpbAt4m5tdWbl_QmTpeZg6aQfmkMuQElzPP2I-9cjU-V4FG_ch5fXE0xtgudsrtjEJsNZlPubamy6RGPrbaUZVKSNTQYFd1ToZuPCPqZTo?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="93" width="624"><figcaption></figcaption></figure>

Some custom nodes may have **dependency conflicts** or require additional Python packages.

**Solution:**

1. Open **Manager** > Locate the failing custom node.
2. Click **Try Update**.
3. Restart **ComfyUI**.
4. If the issue persists, contact **Support** for assistance.

***

**ComfyUI Reconnecting/Disconnected**

Possible Causes & Solutions:

* **Adblocker:** Disable any ad blockers and refresh your browser.
* **Out of Memory (OOM) Exception:** If ComfyUI is unresponsive, try using the queue feature or restart your session.
* **Installing a Custom Node or ComfyUI Restarting:** Wait a few minutes before relaunching the session.

***

**ComfyUI Grey/White Screen**

**Solutions:**

1. Refresh the browser or reload the page.
2. Switch to a different network.
3. If the issue persists, contact **Support**.

***

**Uploaded Model Not Visible**

* If you uploaded a model but cannot see it under the custom node:&#x20;
  * Verify that the file size matches the original source and that the download has fully completed.
  * Refresh your browser. ComfyUI does not automatically update the list of models and custom nodes.

***

**Not able to download gated/restricted models**

* Contact the **Support Team** to assist with downloading restricted models within your workspace.

***

**Generation stuck or cancelled**

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcg52Xh59nJ4huFhpUlv6iXVIsG_zxv6_ByXhmfHUq-s8AFYwcLL71Mpk-4Zl3uoHTM2h410qQylomo3q-l45q9NRynrRAxAHwnhzth7xPui3LoM4XO3FtS9J7nZLD7i8kqkyhTig?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="355" width="589"><figcaption></figcaption></figure>

**Possible Causes & Solutions:**

1. **Failure on Nodes or Missing Config/Files:**
   * Check the node with a red border.
   * Ensure all required models are selected.
   * If the node requires input (image/video), provide the necessary file.
   * Verify that input/output connections are correctly linked.
2. **Out of VRAM/Memory:**
   * Try launching an ULTRA machine.
   * If the issue persists, contact Support.
3. **Unknown Error:**
   * Check logs under comfyui/logs for the root cause.
   * If unresolved, contact **Support**.

***

**Node Not Found in Manager:** Sometimes, the preloaded manager may not be fully synced with the upstream ComfyUI Manager Repository:&#x20;

**Solution:**

* Open ComfyUI Manager > Click Install via Git URL.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfJViPEW6o0lnqoo_lKgsk410DQel-uDTEX6GWbkYBbxxaUx2xrMvxfZiNLjIZ21GYaulc2W4aGHzt5ulUrjnlAYyTB14RnE6PylGuAUBnEjIdg3hipu9jCpn1zXiTkbILD2Tnt0A?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="329" width="576"><figcaption></figcaption></figure>

* Enter the GitHub URL of the custom node in the popup.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdbPr5GIEQL49RlxoP3L_sZCEIugH1ZhZoFXNx1db7IPYJ1lp5PuUs7rg7d6azFY9Behnco9TnXd6uTxsLbRag3JvHlWoiNEfJqydhAHSx8iGYF3CI4T4MjuDVmKwPuXYBFJmwQMQ?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="198" width="445"><figcaption></figcaption></figure>

* Click OK and wait for the installation to complete.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfffAeUcYu0Y-6hEd08wYbzNswVV0kvewiQN8dqmsBR8qzxQ-W-395vPnxuGzPrvRD06VSH4HE0Dbt_PUCsLhl9l4fBPIwfV9fWE6n3G91hG0mkodqcPc-IVFJ1lwji8uD3ZYJBgA?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="180" width="560"><figcaption></figcaption></figure>

* Once installed, click restart.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcbbkOLqTdbGX8Sxo1qnP9CpyLbaTFHJYccBzzil0tk9eZeMnlalKau5xFaoAyIzxkhWpkA6urbj5s-EbVqQiea9YcFlzXk2H4h4AegCYVccA2eFRmHTh4uY_2jQxhWXEpbizTuWQ?key=uCnGXbOFNmqrpko_ecY6fOH5" alt="" height="191" width="553"><figcaption></figcaption></figure>

If the installation fails, reach out to **Support** on [**Discord**](https://discord.gg/hAm87ApunD) for further assistance.

Share:<a href="https://twitter.com/intent/tweet?text=EDU%20%2F%20Teams%20Troubleshooting&#x26;url=https://learn.thinkdiffusion.com/edu-teams-troubleshooting/" class="button secondary"></a><a href="https://www.facebook.com/sharer.php?u=https://learn.thinkdiffusion.com/edu-teams-troubleshooting/" class="button secondary"></a><a href="https://www.linkedin.com/shareArticle?mini=true&#x26;url=https://learn.thinkdiffusion.com/edu-teams-troubleshooting/&#x26;title=EDU%20%2F%20Teams%20Troubleshooting&#x26;source=ThinkDiffusion" class="button secondary"></a><a href="mailto:?subject=EDU%20%2F%20Teams%20Troubleshooting&#x26;body=https://learn.thinkdiffusion.com/edu-teams-troubleshooting/" class="button secondary"></a><br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.thinkdiffusion.com/thinkdiffusion-edu-teams/edu-teams-commonly-asked.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.