Troubleshooting decision tree

First: protect the customer

Pause a campaign, sender, agent, workflow, schedule, or public traffic when continued execution could duplicate contact, publish wrong content, expose data, or increase cost. Record the time and scope before changing configuration.

1. Check platform status

Open Spacebrain system status. If an incident matches the feature and time, avoid repeated retries and follow updates.

2. Confirm context

• Correct Spacebrain account and active workspace or sub-account.
• Correct role and feature availability.
• Correct module, view, channel filter, date range, timezone, and search.
• Correct provider organization and resource.

3. Reproduce safely

Use one internal test record and record the exact steps, URL, time, expected result, and actual result. Refresh once. Try a private browser window when session or extension state is suspected. Do not clear or delete production data merely to reproduce.

4. Locate the boundary

Ask where evidence stops:

• Does the record exist in Spacebrain?
• Did the trigger fire?
• Did the workflow node run?
• Did Spacebrain accept the provider action?
• Does the provider show the item?
• Did the customer destination receive it?

This separates a UI filter issue from configuration, authorization, provider delivery, or recipient behavior.

5. Read the exact error

Capture the complete message, status, affected object identifier, and timestamp. Redact content and secrets. Do not paraphrase away provider codes that support may need.

Common UI checks

• Save pending edits and refresh.
• Sign out and back in after a role or workspace change.
• Disable browser translation or content-blocking for a controlled test.
• Confirm JavaScript, cookies, pop-ups, and OAuth redirects are permitted for the sign-in flow.
• Test a supported current browser.

Continue with communication and automation troubleshooting or contacting support.