WORKLOAD_DISABLED
What triggered it
Section titled “What triggered it”VibeCord can temporarily disable specific workload types, usually for one of two reasons:
- A launch workload is hitting issues — e.g. a Luanti deploy bug we want to debug before more users hit it
- An upstream provider is down — e.g. a hosting provider is undergoing maintenance
When that’s set, you see WORKLOAD_DISABLED on new generations or deploys for that workload.
What to try
Section titled “What to try”1. Check the status page. status.vibecord.dev — known platform issues are posted there.
2. Try a different workload. If one workload is disabled but another is fine, you can keep building the other side of your community while it recovers.
3. Wait — most disables are short. Workload disables should clear when the incident or operational check does.
When to contact support
Section titled “When to contact support”If a workload is disabled for 24+ hours and the status page is green:
- Drop a note in Discord
#help - Or email founder@vibecord.dev
If the same workload is repeatedly disabled, tell us in Discord so we can link the status update to the underlying fix.
Check status page