MQTTAsync_failureData(3)

✨ MQTTAsync_failureData ✨

okay bestie, welcome to MQTTAsync_failureData(3) — a little struct from the Library Functions Manual that shows up exactly when things did not go your way 🫶 it's giving "the breakup text of the MQTT world" but like, in C 💅

---

🌸 NAME 🌸

MQTTAsync_failureData — the lil container that holds all the tea about a failed API call 💀

---

🎀 SYNOPSIS 🎀

#include <MQTTAsync.h>

💖 Data Fields 💖

MQTTAsync_token token
int code
const char * message

---

🦋 Detailed Description 🦋

So here's the vibe: this is the data you get back when an API call fails, handed to you in the response callback onFailure 😭 like, the callback is literally named onFailure, it's not subtle, it's not playing games, it's telling you straight up.

Bestie this is the sad-path struct. Success has its own moment, this one is for when the request said "no ❤️". The way that every field here exists purely to explain what went wrong? iconic. not fun, but iconic. ✨

---

🌈 Field Documentation 🌈

• MQTTAsync_token token — a token that identifies the failed request 🎟️ like a little name tag for the specific call that didn't slay.
• int code — a numeric code identifying the error 🔢 the receipts, in number form. iykyk.
• const char* message — optional text explaining the error 💬 and heads up, it can be NULL. so do a vibe check before you dereference it, bestie, fr fr 🙈

---

👑 Author 👑

Generated automatically by Doxygen for the Paho Asynchronous MQTT C Client Library, straight from the source code 🧚 no human hand wrote this, the robots did it and honestly? they ate. 💅

---

k bye bestie, that's the whole page! 🌸 this was pulled from the Paho Asynchronous MQTT C Client Library, dated Tue Jun 2 2026 00:00:00 🎀 go forth and handle your failures gracefully, main character 💖🦋✨