After a trap is sent to the server, it remains in the 'createdTraps' queue.
Fairly sure this issue is caused by a differing hash code between when the trap is first added to the queue & when it's successfully created, as the hash code is calculated based partially on the ID of the Trap (and the ID gets set when a 201 response is received from the server).
After a trap is sent to the server, it remains in the 'createdTraps' queue.
Fairly sure this issue is caused by a differing hash code between when the trap is first added to the queue & when it's successfully created, as the hash code is calculated based partially on the ID of the Trap (and the ID gets set when a 201 response is received from the server).