# Return Code on Mesh.Publish

**URL:** <https://community.particle.io/t/return-code-on-mesh-publish/53296>\
**Category:** BLE // NFC\
**Tags:** boron, argon, xenon\
**Created:** [November 15, 2019, 9:24am UTC](https://community.particle.io/t/return-code-on-mesh-publish/53296 "2019-11-15T09:24:49Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![kubark42](https://avatars.discourse-cdn.com/v4/letter/k/848f3c/32.png) [@kubark42](https://community.particle.io/u/kubark42)\
**Post date:** [January 12, 2020, 4:41pm UTC](https://community.particle.io/t/return-code-on-mesh-publish/53296/5 "2020-01-12T16:41:56Z")

</div>

> For ‘Reliable’ read ‘Meaningful’.

Here's a discussion on the values it can return, [Mesh.publish() successful but returns false even though gateway receives message - #7 by kubark42](https://community.particle.io/t/mesh-publish-successful-but-returns-false-even-though-gateway-receives-message/46664/7).

I personally would love an API which includes an ACK for a specific receiver. This way a mesh could have sleepy elements which only wake up long enough to ensure their messages is delivered to the gateway, without considering if the gateway is currently able to publish the message online.

It's trivial to build an ACK of this form, but since there is already a mechanism to ensure that _a_ gateway gets (and forwards to the cloud) the mesh's `Particle.publish()` command, it would be nice if this API could be exposed to `Mesh.publish()` as well.

---

_[View the full topic](https://community.particle.io/t/return-code-on-mesh-publish/53296)._