Warnings and an offline bot

Quick checks

1. Check the selected channel.
2. Open Channel setup.
3. Check the tool switch and bot status.
4. Complete the Twitch action offered by the page.
5. Open Alerts.
6. Read the newest active alert.

• BlokeBot normally identifies an absent channel.
• BlokeBot normally identifies an absent permission.
• BlokeBot normally identifies an absent connection.
• BlokeBot normally identifies an absent tool.

Common Twitch failures

• If Twitch uses the wrong account, sign out of Twitch in the pop-up. Repeat the specific Channel or Bot connection action.
• If a moderator-only action is unavailable, check that the bot is still a moderator. If its grant predates the required scope, reconnect.
• For a follower-only rejection, make the bot a moderator or follow the channel manually as the bot account.
• If Twitch rejects an announcement, check that the bot is still a moderator. Reconnect the bot account with the action in Channel setup.
• If a dashboard script or stylesheet is absent, ask the server owner to check proxy paths and static assets. Do not reconnect Twitch repeatedly.

Information for support

If the problem remains, send the page name and channel to the server owner. Do not send Twitch secrets or tokens.

• Include the time.
• Include the alert text.
• Include the support reference.

Plugin failures

• After Remove, no plugin settings remain.
• After Remove, no private data remains.
• After Remove, no page remains.
• After Remove, no flow remains.
• After Remove, no run history remains.
• After Remove, no receipt remains.
• After Remove, no context remains.
• After Remove, no latest outcome remains.
• If the marketplace is unavailable, wait for one successful catalog refresh. If Admin shows an older snapshot, search can still use it.
• If Install or Update is unavailable, check GitHub access and the tag. An absent or moved tag needs a corrected catalog entry or package release.
• For a validation fault, correct the reported cause.
• The manifest is a possible cause of a validation fault.
• Package declarations are a possible cause of a validation fault.
• Target support is a possible cause of a validation fault.
• Also check paths.
• Also check links.
• Also check collisions.
• Also check size limits.
• For a migration or activation fault, read the latest operation message. The old code cannot resume after durable migration starts.
• For a worker fault, BlokeBot tries one automatic restart. After the next fault, correct the cause. Select Restart.
• Needs attention: complete the required Twitch scope or EventSub action. Independent work can remain available.
• If a command is absent, check built-in and custom commands first. Those routes shadow a plugin command.
• If BlokeBot rejects feature enablement, correct the reported cause.
• A possible cause is a plugin command collision.
• A possible cause is an invalid automatic flow.
• A possible cause is an existing flow name.
• If an automatic flow is deleted, disable the feature. Enable it again to create the flow again.

• Recover a plugin installation
• Recover a channel plugin feature

Privacy and data requests

The privacy notice is the authoritative description of stored data.

• The privacy notice covers Twitch data for both origins.
• The privacy notice covers cookies for both origins.
• The privacy notice covers browser storage for both origins.
• The privacy notice covers retention for both origins.
• The control for this help site's preferences is on the privacy notice itself.
• The dashboard's control is in its account menu: Stop saving view preferences. Each origin's control governs only that origin's storage.
• Send private data requests to the privacy contact in the notice. Do not send them to chat or a public board.

• Read the privacy notice