Troubleshooting
Common Growth questions and what's actually going on behind them.
How to read this page
Most of what looks like a bug in Growth is actually the system being honest about a limit it has on purpose. This page walks through the questions that come up most often.
Why can't I send this email?
The task modal will tell you exactly why, but the usual reasons are: the client has an active do-not-contact flag, there's no email address on file for them, or your location hasn't connected a real mailbox yet in Growth Settings. Growth never fakes a send. If email isn't available, it says so instead of pretending to work.
Why does this email need review before I can send it?
Emails referencing a specific quoted price require review by default, along with any workflow you've explicitly set to review-required. This is intentional: a human should read anything with a dollar figure attached before it reaches a client.
Can I see if a client replied to a sent email or text?
No, not inside Nabu. Growth doesn't have access to your team's actual email inbox or SMS system, so once a message goes out, it has no way to detect a reply on its own. The task sits in Waiting for client until someone checks the real inbox or phone and comes back to record what happened. See Task Status and Lifecycle for more on why this is by design rather than a missing feature.
Where did my task go after I marked it done?
Once a task's status is Closed, it drops off the queue entirely. There isn't a history or archive view to browse it in yet. If a task seems to have vanished, check whether someone already recorded an outcome on it.
The action button says something I didn't expect
The button reflects what's actually left to do, not just the channel. An email task that's already been sent will say "Log reply" instead of "Review email," because there's nothing left to review, only a result to record once you have one.
A role shows a "Not configured" warning
This means a workflow is pointed at a role that doesn't exist as a real role at your location yet (for example, a title your team uses informally that hasn't been set up as a system role). Tasks still get assigned, using a fallback role, but the warning is there so you know the setting needs attention.
Why can't I claim this task?
A task can't be claimed if someone else already has it (Growth won't let two people claim the same task) or if it's fully automated, in which case there's no claim step, only a fallback role in case automation fails.
What does "Generated by Nabu" mean?
It means the task's execution mode is automated: Nabu is handling it directly rather than assigning it to a person. It still has a real role attached underneath, which only comes into play if the automated send fails and the task needs to be handed to someone.
General questions
Why is the "Save changes" button in Growth Settings disabled? It stays disabled until you've actually changed something, and it re-disables after a save. If you've made a change and it's still greyed out, check for a validation warning elsewhere on the page. It won't let you save while there's an unresolved configuration issue, even one in a section you're not currently looking at.
Where do I go if this page didn't answer my question? See Getting Help to open a support ticket. Include which task or client was affected and what you were expecting to happen.