Skip to main content
Solved

Device Hub printing 2 copies of label

  • September 4, 2024
  • 8 replies
  • 250 views

dsimmerly
Pro I
Forum|alt.badge.img+1

Customer is reporting that when printing carrier labels from Easy Post to Device Hub there are 2 copies of the same label printed

 

- there is only one job created

 

- the printer is configured to print 1 copy

 

- is has been confirmed the zpl label file only contains only one label

 

- the printer has been reset 

 

 

What could cause this issue?  How can this be resolved

Best answer by schneur96

Hi

Were are on 24R2

Acumatica sends print jobs to Device Hub using push notifications (NT). Device Hub also has a polling (POLL) mechanism as a fallback in case a push notification is missed.

In our logs, we saw cases where push and polling were triggering almost simultaneously. Polling would sometimes pick up the job before Device Hub had time to confirm successful processing back to Acumatica, which caused the same job to be processed twice—resulting in duplicate prints.

Our review:

  • Only one print job was created in Acumatica

  • Printer was set to print a single copy

  • Label/ZPL file contained only one label

  • Print timing was consistent with historical behavior

What we recommend checking/trying:

  • Review Device Hub push notification and polling settings

    • Confirm both are enabled

    • Make sure polling is not set too aggressively

  • Increase the polling interval

    • We extended polling from ~30 seconds to ~90 seconds

    • We also excluded the last 10–15 seconds of the polling window to give push notifications time to complete

 

After making these changes, the issue still happens, but not very often.

8 replies

darylbowman
Captain II
Forum|alt.badge.img+16

Using Task Manager, make sure there isn’t more than one instance of DeviceHub running on the same machine or even DeviceHub running on multiple machines.


hkabiri
Acumatica Moderator
Forum|alt.badge.img+8
  • Acumatica Support Team
  • September 4, 2024

@dsimmerly This might be the issue related to using both Push Notification and regular polling and when the initial job status not updated before the wait time, it tries again and that result into duplicate copy.

What version and build Client using both ERP and DeviceHub?

 

 


Steve Lemmler
Freshman I
  • Freshman I
  • September 20, 2024

DId not see an answer to this. We are also seeing this. We just upgraded to 2024 r1 and that is when it started. Part of the upgrade required a new version of Device Hub.

 

Is polling and push settings the issue ?


  • Freshman I
  • December 13, 2024

We are also having this issue and are currently on 2024 R1. How do you check push notification and polling settings?


Steve Lemmler
Freshman I

Found out due to error handling on the end of the API calls, we where calling a second time. Did not see it until we where seeing duplicate requests.


darylbowman
Captain II
Forum|alt.badge.img+16

@morrowhe - It’s in the DeviceHub utility’s configuration settings


  • Freshman II
  • December 29, 2025

I see the push notification and polling settings. How do the settings affect the printing? What settings might cause duplicate labels to be printed?

Thanks, Tom


Forum|alt.badge.img
  • Pro I
  • Answer
  • December 30, 2025

Hi

Were are on 24R2

Acumatica sends print jobs to Device Hub using push notifications (NT). Device Hub also has a polling (POLL) mechanism as a fallback in case a push notification is missed.

In our logs, we saw cases where push and polling were triggering almost simultaneously. Polling would sometimes pick up the job before Device Hub had time to confirm successful processing back to Acumatica, which caused the same job to be processed twice—resulting in duplicate prints.

Our review:

  • Only one print job was created in Acumatica

  • Printer was set to print a single copy

  • Label/ZPL file contained only one label

  • Print timing was consistent with historical behavior

What we recommend checking/trying:

  • Review Device Hub push notification and polling settings

    • Confirm both are enabled

    • Make sure polling is not set too aggressively

  • Increase the polling interval

    • We extended polling from ~30 seconds to ~90 seconds

    • We also excluded the last 10–15 seconds of the polling window to give push notifications time to complete

 

After making these changes, the issue still happens, but not very often.