Failure to update 1+n scan configuration in Manage Scans

[secbyd]

• Editing and updating first scan completes successfully.
• Editing and updating second scan fails

Update button changes to "Updating..." but process does not complete.
Closing and reopening the editing page does not help. The edit page does actually show the proposed changes but fails to store them in the back-end/represent them on the overview page.

A full refresh of the page is the only option.

[MrSeccubus]

After running t/53_scans in the first workspace editing the first scan works, but editing the second scan doesn't.
PUT /api/workspace/100/scan/3
JSON:

{"findCount":"","lastScan":null,"name":"nessusZ","notifications":"0","parameters":"paramsZ","password":"passwordZ","runs":"0","scanner":"Nessus6Z","targets":"localhost\\n127.0.0.1","workspace":"100","id":"1"}

response:

{"message":"A scan named nessusZ already exists in this workspace at lib\/Seccubus\/Scans.pm line 253.\n","status":"Error"}

[MrSeccubus]

If I update the second scan first, things work out ok.
PUT /api/workspace/100/scan/3

{"findCount":"","lastScan":null,"name":"nessusZ","notifications":"0","parameters":"paramsZ","password":"passwordZ","runs":"0","scanner":"Nessus6Z","targets":"localhost\\n127.0.0.1","workspace":"100","id":"1"}

[MrSeccubus]

It looks like it is somehow confusing IDs

[MrSeccubus]

Apparently their is some weird caching going on. url to the api funcitons seems to be passed by reference and not by value as I had expected. Therefore the funciton was changing what should have been a constant.