Help Center: Long-Running Work and Job Status
Help Center: Long-Running Work and Job Status
Some Swayd actions take longer than a page request: brand onboarding, signal mining, Review Desk generation, and slide rendering.
These now run as durable jobs in Swayd’s database.
What you will see
What is not instant
Do not refresh repeatedly to “make it faster”; use the status shown on the item.
If something stays queued
The founder can inspect the job queue in the admin console. A queued job means the worker is not running; it is not lost.
If something fails
The error is recorded. The founder can retry the job or fix the upstream service. Your credits are not silently consumed by a failed job once credit reservations are fully wired; until then, check with support before retrying a paid render.
FAQs
Can I close the tab?
Yes, after the action is accepted.
Will I be charged if it fails?
Failed jobs should release reserved credits. That release is being completed in Wave 2; ask support if a failure consumed credits.
Why is the status still “queued”?
The worker process may be stopped. The job is durable and will run when the worker is back.
Can I cancel?
The founder can cancel a queued/running job from /admin/jobs.
Where do I see errors?
The affected item shows the error; the founder can inspect the job’s error in /admin/jobs.
Related Guides & Tutorials
Reach out to our creative support team at support@tryswayd.com.