The way the script is written, it assembles the payload then it checks for an internet connection. If there is connection, the payload is sent and you see "Payload Published". If there is no internet connection, the Payload is saved to the /usr directory. Once internet connection is detected, the script will go back to the /usr directory, grab any payloads, then send those out forst then will go back to grabbing new payloads. There may be a loss of data packets while the system is grabbing saved payloads as it can't do that and process live payloads at the same time. Once the saved payloads are sent, things go back to normal.

This is usually caused by the internet on site  glitching in and out, which is why the saved section of the script is being activated.