tester-troubleshooting

Diagnose Braze push, segment, in-app, and API delivery failures.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill tester-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tester-troubleshooting
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/tester-troubleshooting
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill tester-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a single, structured diagnostic guide to identify root causes and resolve delivery failures for pushes, in-app messages, banners, segments, API/webhook errors, and race conditions across Braze campaigns and Canvases. It reduces time-to-resolution by directing investigators to the correct failure layer, offering targeted checks for token ownership, segment reachability, payload limits, platform error codes, and network connectivity.

Core Features & Use Cases

  • Layered diagnostic workflow: Step-by-step checks from user eligibility and push registration through segment computation, platform-specific error codes, and infrastructure/network verification.
  • Error-code mappings and remediation: FCM and APNs error tables, API 4XX/5XX guidance, Braze-specific simulated codes (e.g., 598), and concrete resolution steps.
  • Race-condition and timing guidance: Detection patterns and fixes for ordering issues, Canvas delays, synchronous vs asynchronous API calls, and delivery validations.
  • Use Case: A QA engineer uses the guide to triage a non-delivering push by verifying push registration, token validity and ownership, segment filters, payload size, and then mapping observed server error codes to remediation steps.

Quick Start

Ask the tester-troubleshooting skill to run a systematic diagnosis for a failing push, segment, in-app message, or API error by providing the affected user ID, app, and observed error or symptom.

Frequently Asked Questions about tester-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Braze push notification delivery failures?

Diagnose Braze push delivery failures by running a systematic workflow that checks push token registration, user eligibility, segment filters, payload size limits, and maps FCM or APNs error codes to targeted remediation steps.

What do Braze API error codes like 598 mean and how do I resolve them?

Braze API error codes, including 4XX, 5XX, and simulated 598 responses, indicate webhook or API delivery failures that require mapping observed server error codes to targeted resolution steps for remediation.

How do I fix race conditions and timing issues in Braze Canvas operations?

Fix Braze Canvas race conditions by applying detection patterns for ordering issues and delays, then validating synchronous versus asynchronous API calls and delivery sequencing to correct timing failures.

Why are my Braze in-app messages not showing up for targeted segments?

Braze in-app messages fail to deliver when segment computation errors occur or user eligibility criteria are unmet, requiring step-by-step checks of segment reachability and filter complexity to resolve the failure.

Can I diagnose Braze webhook and API connectivity issues without running external scripts?

Yes, you can diagnose Braze webhook and API connectivity issues without external scripts by using structured DNS checks, connectivity tests, and error-code mappings to identify network or infrastructure failure layers.

What is the best way to triage a non-delivering Braze push campaign?

The best way to triage a non-delivering Braze push campaign is to systematically verify push registration, token validity and ownership, segment filters, payload limits, and server error codes to pinpoint the failure layer.