# Troubleshooting with ManyMoney AI

This guide explains how to troubleshoot issues with [ManyMoney AI](/product/pushwoosh-ai/ai-assistant/). When you provide structured information in your prompts, ManyMoney AI can diagnose faster and suggest more precise fixes.

<Aside type="tip">
If you need human support, you can [submit a ticket](https://help.pushwoosh.com/hc/en-us/requests/new) to Pushwoosh Support.
</Aside>

## What ManyMoney AI can inspect

ManyMoney AI uses Pushwoosh APIs to inspect:

| Category <div style="width:160px"></div> | What it inspects <div style="width:320px"></div> |
| --- | --- |
| Journey | Configuration and validation, stats by journey point, user flow for a specific user |
| Message delivery | Tracking logs for delivery status and error codes, message and campaign statistics, delivery and error reports |
| Users and devices | Device registration and status, user tags, [segment](/product/audience-data-and-segmentation/segmentation/) compilation and size |
| Configuration | Application and platform settings, presets (push, email, etc.), segment and event logic |


## How ManyMoney AI diagnoses issues

When you describe a problem, ManyMoney AI:

1. Gathers diagnostic information using Pushwoosh APIs and your project data.
2. Checks multiple failure points (journey configuration, presets, segments, platform settings).
3. Identifies the root cause from patterns in the data.
4. Suggests step-by-step resolution and explains why the issue occurred so you can avoid it in the future.

### What to expect from ManyMoney AI's diagnosis

In the response you get:

* Primary issue and current state of your project
* Why it is not working and fix options (with pros and cons)
* Any additional issues found
* For actions that change your account, ManyMoney AI asks for explicit confirmation before proceeding

**Response time:** Typically 10–30 seconds for a full diagnosis.


## Do's and don'ts when troubleshooting with ManyMoney AI

Include the right details in your prompt so ManyMoney AI can diagnose effectively. The more accurate and complete your prompt, the quicker you get to a solution.

| Do <div style="width:280px"></div> | Do not <div style="width:280px"></div> |
| --- | --- |
| **Copy exact error messages** instead of paraphrasing. | Paraphrase errors (e.g. "it said something about invalid"). |
| Include **journey URLs** (copy from your browser when the journey or resource is open) so [Journey ID](/developer/api-reference/api-identifiers/#journey-id) and names can be taken from them. | Assume ManyMoney AI knows your setup ("the usual configuration"). |
| Specify **timezone** when the issue involves timing or scheduling (e.g. UTC, Europe/Moscow). | Omit platform (iOS, Android, Web, etc.). |
| Share **relevant dates** (e.g. "started Monday" or "since we updated on Jan 15"). | Say "it does not work" without describing expected vs actual behavior. |
| Mention **what you have already tried** so repeated steps can be skipped. | Mix several unrelated issues in one prompt. |

<Aside type="tip" title="Follow up in the same conversation">
Some issues need several rounds. Keep the same conversation and add each new finding so ManyMoney AI can build on it.
</Aside>

## Prompt templates by issue type

Use the templates below as checklists so your prompt has everything ManyMoney AI needs for diagnosis. To find identifiers, see [Key API identifiers](/developer/api-reference/api-identifiers/).



### Push notification delivery

**Use when:** Push notifications are not delivered on iOS, Android, or Web.

Include these details in your prompt to ManyMoney AI:

| Include in prompt <div style="width:180px"></div> | Example or format <div style="width:200px"></div> |
| --- | --- |
| Platform | iOS, Android, or Web |
| Journey | [Journey ID](/developer/api-reference/api-identifiers/#journey-id) or full Control Panel URL if applicable |
| When it started | Date and time, or "never worked" |
| Error | Exact message, if any |
| Test device | [Hardware ID](/developer/api-reference/api-identifiers/#hardware-id) (HWID) if testing on a specific device |
| Expected | What should happen |
| Actual | What happens instead |

<Aside type="tip" title="Example prompt">
Push notifications for iOS are not delivering in the "Welcome Flow" journey.

* Journey: `https://app.pushwoosh.com/journeys/{APP_CODE}/{STATUS}/{JOURNEY_UUID}`
* Started: Yesterday at 2pm
* Error: Users appear in journey stats but no push is received
* Test device HWID: test-iphone-12-hwid
* Expected: Push sent right after user registers
* Actual: User enters the journey but no notification appears
</Aside>

### Email delivery

**Use when:** Emails are not delivered or bounce.

Include these details in your prompt to ManyMoney AI:

| Include in prompt <div style="width:180px"></div> | Example or format <div style="width:200px"></div> |
| --- | --- |
| Campaign or journey | Name or [UUID](/developer/api-reference/api-identifiers/#journey-id) |
| Email template | Name or [email content code](/developer/api-reference/api-identifiers/#email-content-code) |
| From address | sender@yourdomain.com |
| Domain verification | Verified, not verified, or unknown |
| Who is affected | All users, a [segment](/product/audience-data-and-segmentation/segmentation/), or test emails only |
| Bounce type | Hard, soft, complaint, or unknown |
| When it started | Date or "never worked" |
| Test email | test@example.com if testing |

<Aside type="tip" title="Example prompt">
Emails are not being delivered in the "Abandoned Cart" journey.

* Journey: `https://app.pushwoosh.com/journeys/{APP_CODE}/{STATUS}/{JOURNEY_UUID}`
* Email template: "Cart Reminder Day 1"
* From: noreply@mystore.com
* Domain verification: Shows "NOT READY"
* Recipients: All users
* Started: Today when the journey was launched
</Aside>

### Customer journey not working

**Use when:** A journey shows no or unexpected activity.

Include these details in your prompt to ManyMoney AI:

| Include in prompt <div style="width:180px"></div> | Example or format <div style="width:200px"></div> |
| --- | --- |
| Journey name, URL or UUID | Full URL or [Journey ID](/developer/api-reference/api-identifiers/#journey-id) |
| Status | Draft, Inactive, Active, Paused, or Archived |
| Entry type | [Trigger-based](/product/customer-journey/journey-elements/entry-elements/trigger-based-entry/), [audience-based](/product/customer-journey/journey-elements/entry-elements/audience-based-entry/), or [API-based](/product/customer-journey/journey-elements/entry-elements/api-based-entry/) |
| Entry event or segment | [Event name](/developer/api-reference/api-identifiers/#event-name) or [Segment name](/developer/api-reference/api-identifiers/#segment-filter-name) |
| Expected users | Approximate number or "should have entered" |
| Date range | Period you are looking at in stats |
| Last change | If you changed something recently |

<Aside type="tip" title="Example prompt">
Customer journey shows no activity.

* Journey: "Black Friday 2024 Campaign"
* URL: `https://app.pushwoosh.com/journeys/{APP_CODE}/{STATUS}/{JOURNEY_UUID}`
* Status: Active (started 2 days ago)
* Entry type: Trigger-based
* Entry event: "AddToCart"
* Expected: At least 100 users should have entered
* Date range: Last 7 days
* Last modified: Send time was changed yesterday
</Aside>

### Segmentation issues

**Use when:** A segment does not match the expected users.

Include these details in your prompt to ManyMoney AI:

| Include in prompt <div style="width:180px"></div> | Example or format <div style="width:200px"></div> |
| --- | --- |
| Segment name | Name of the segment as shown in Control Panel (e.g. "High-Value Customers") |
| Segment criteria | Description of the filter conditions |
| Expected size | Approximate number of users you expect |
| Actual size | Segment size as shown in Control Panel, or "error" if it fails |
| Tags or events | [Tag](/developer/api-reference/api-identifiers/#tag) and [event](/developer/api-reference/api-identifiers/#event-name) names used in the segment |
| Error message | Exact message if segment creation or compilation failed |
| Use case | What you are trying to target (e.g. VIP offer, reactivation) |

<Aside type="tip" title="Example prompt">
Segment does not match expected users.

* Segment: "High-Value Customers"
* Filter: Users with "Total Purchases" greater than $500 in the last 90 days
* Expected: About 1,000 users
* Actual: 0 users
* Tags used: "Total Purchases" (should be PRICE type)
* Error: Filter compiles but returns no matches
* Use case: Targeting VIP customers for an exclusive offer
</Aside>

### Integration and SDK issues

**Use when:** Registration, tags, events, or push receipt fails in your app.

Include these details in your prompt to ManyMoney AI:

| Include in prompt <div style="width:180px"></div> | Example or format <div style="width:200px"></div> |
| --- | --- |
| Platform | iOS, Android, Web, React Native, or Flutter |
| SDK version | Version number |
| Framework | Swift, Objective-C, Kotlin, Java, JavaScript, etc. |
| Issue | Specific problem |
| What works | Steps that succeed |
| What fails | Steps that fail |
| Error logs | Full error text |
| Code snippet | Relevant code, if useful |
| Tested on | Device, emulator, or production |

<Aside type="tip" title="Example prompt">
SDK integration issue on iOS.

* Platform: iOS 16+
* SDK version: Pushwoosh 6.5.2
* Framework: Swift
* Issue: Device registers but tags are not saved
* Works: Push token registration, receiving notifications
* Fails: `sendTags()` calls appear to be ignored
* Error logs: None, but tags do not appear in Control Panel
* Code: `pushwoosh.sendTags(["userId": "12345", "premium": true])`
* Tested on: iPhone 14 Pro simulator and physical device
</Aside>

### Analytics and reporting

**Use when:** You need to understand a metric or report.

Include these details in your prompt to ManyMoney AI:

| Include in prompt <div style="width:180px"></div> | Example or format <div style="width:200px"></div> |
| --- | --- |
| Metric or report | Name of the metric or report (e.g. Delivery rate, Journey exits) |
| Time period | Date range (e.g. Last 7 days, January 2024) |
| Filters | [Journey](/product/customer-journey/pushwoosh-journey-overview/), [segment](/product/audience-data-and-segmentation/segmentation/), or platform |
| Current value | Value or message you see in Control Panel |
| Expected | What you expected or "need to understand" |
| Decision impact | How you will use this data |

### Performance and speed

**Use when:** An operation is slow or times out.

Include these details in your prompt to ManyMoney AI:

| Include in prompt <div style="width:180px"></div> | Example or format <div style="width:200px"></div> |
| --- | --- |
| Operation | What is slow (e.g. segment compilation) |
| When | Always, at peak times, or for a specific action |
| Volume | How many users or messages are affected |
| Timing | How long it takes vs what you expect |
| Impact | Business impact |
| Recent changes | Anything changed before the issue started |

## Proactive checks

You can ask ManyMoney AI for a proactive audit. Examples of prompts you can use:

* **Journey:** "Audit my journey configuration for potential issues. Journey: `name or UUID`. Focus: `delivery`, `performance`, `user experience`, or `all`."
* **Email:** "Check my email setup for deliverability issues. Application: [application code](/developer/api-reference/api-identifiers/#application-code). I send from: `your from address, e.g. noreply@mystore.com`. Lately: `e.g. bounces in the last 2 weeks, or no issues`."
* **Campaign:** "Analyze campaign performance and suggest improvements. Journey or campaign: `name or UUID`. Current metrics: `what you see`. Goals: `what you want to achieve`."