Slow or Stuck Module Output

Occasionally, a module (Organic, Paid, or Reporting) may take longer than expected to generate output. While rare, these moments are typically temporary and can be resolved with a few simple steps.

This guide walks through how to diagnose and resolve performance slowdowns inside YG3.


Typical Output Times

These durations may vary based on system load, content complexity, or input volume.


Common Causes of Delay

1. Heavy Server Load

High usage volume (e.g. during peak hours) may briefly delay content generation.

Solution:
Wait 1–2 minutes before retrying. YG3 automatically queues and completes processes even during load spikes.


2. Incomplete Inputs

If required inputs are missing, generation may pause or silently fail.

Solution:


3. Too Much Input or Overloaded Prompt

Excessively long inputs (e.g. large datasets, pasted reports) may cause delays or timeouts.

Solution:


4. Connection or Browser Instability

Sometimes, browser memory or network interruptions may cause the module to stall.

Solution:


Best Practices to Prevent Module Freezing


If a Module Is Fully Stuck

If a module stays frozen for more than 3 minutes:

  1. Refresh your browser tab

  2. Retry the action

  3. If the issue repeats, contact support with:

    • Module name

    • Time of issue

    • Screenshot (if possible)


Tip: Use Elysia While You Wait

If a module is processing slowly, open a thread with Elysia and start discussing next steps, campaign framing, or strategic options. You don’t have to pause your momentum.


YG3 is Built to Self-Recover

Most stalls resolve with a refresh or updated input.
Modules are designed to auto-timeout and requeue when load is high—so you won’t lose work.

Stay patient, stay focused, and if needed, escalate.

Published with Nuclino