Discord Bot Platform  ·  View 04 of 19  ·  People and journeys

Journey — Developer, First Bot

The trough is the silent failure: a bot that connects and receives nothing.

Editable source SVG draw.io All views
Bot developer first application Goal — Have my bot answer /ping in a real server tonight Trigger — A friend's server needs a custom command Done when — The command works, and I can see why when it does not 1 · Register dev portal 2 · Install ◆ moment of truth 3 · Connect 4 · First command ◆ moment of truth 5 · Grow What they do Creates application Copies token Builds invite link Picks permissions Opens a socket Identifies Registers /ping Types /ping Joins 100 servers How it feels Excited Fine Stuck Where it hurts Scopes are unclear Intents silently empty "Application did not respond" Review gate for content What the platform gives Public key + token once Consent screen lists scopes Close code names the cause Test interaction + logs Limit warnings at 75% Journey — Developer, First Bot The trough is the 3-second acknowledgement: the platform can only show the user a failure, so the developer needs the reason. v 1.0 · owner Integration Platform Architecture · date 2026-10

Where it fails

  • Intents silently empty: an unapproved or undeclared intent yields no events and no error. The close code and portal warning exist because of this moment (ADR-02).
  • "Application did not respond" is the user's message, not the developer's reason.

What answers it

  • Close codes that name causes, a signed test-interaction tool, and per-application ack-in-3s rates in the dashboard (view 16).
◀  Actors and Core Journeys All views Journey — Member, Runs a Slash Command  ▶
Solution Architecture v1.0 · Microsoft Azure · Integration Platform Architecture · 2026-10 · 19 views · 12 architecture decision records04-journey-first-bot