# APM Failed to publish events: temporary bulk send failure / Queue is full 503 error **URL:** https://discuss.elastic.co/t/apm-failed-to-publish-events-temporary-bulk-send-failure-queue-is-full-503-error/202884 **Category:** APM **Tags:** server **Created:** [October 9, 2019, 5:16pm UTC](https://discuss.elastic.co/t/apm-failed-to-publish-events-temporary-bulk-send-failure-queue-is-full-503-error/202884 "2019-10-09T17:16:02Z") **Posts on this page:** 1 **Showing post:** 7
### Author: ![jalvz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jalvz/32/45613_2.png) [@jalvz](https://discuss.elastic.co/u/jalvz) #### Post date: [October 14, 2019, 12:45pm UTC](https://discuss.elastic.co/t/apm-failed-to-publish-events-temporary-bulk-send-failure-queue-is-full-503-error/202884/7 "2019-10-14T12:45:35Z")
Hi, unfortunately I don't have a date, but it will be released soon. In case you didn't see it already in the link you posted above, another option is to use a processor to drop that field completely, as my colleague explained here: > [@APM: 503 Queue is full, server sleeping, nothing helps](https://discuss.elastic.co/t/apm-503-queue-is-full-server-sleeping-nothing-helps/203180/4): > > APM does not keep logs at all Do you mean that you have disabled keeping logs? By default the APM Server does write to [log files](https://www.elastic.co/guide/en/apm/server/current/configuration-logging.html). I assume you might encounter a similar bug to what we have seen in another discuss entry ([APM Failed to publish events: temporary bulk send failure / Queue is full 503 error](https://discuss.elastic.co/t/apm-failed-to-publish-events-temporary-bulk-send-failure-queue-is-full-503-error/202884)). From 7.4 on apm pipelines are enabled by default, and a new field client.ip is indexed. Providing invalid data for fields that are part of the pipelines, can lead to errors and ingestion re… Hope that helps and sorry again. --- _[View the full topic](https://discuss.elastic.co/t/apm-failed-to-publish-events-temporary-bulk-send-failure-queue-is-full-503-error/202884)._