Hi Jasper. I was told privately that was fixed, and can confirm it's working now!
Thanks a lot for your promptly help. Best, Hugo On 12:15 30/08, Jasper den Hertog wrote: > hi Hugo, > > Thanks for this feedback, I can confirm this is a bug. I was able to > reproduce this. > > You’ve hit (regression) bug, probably due to (massive) changes we have made > to our backends recently. > > We have started figuring out what causes this and come up with a solution. > I’ll keep you posted on progress we’re making. > > Sorry for the inconvenience this has caused, > > greetings, > > Jasper den Hertog > > > On 29 Aug 2019, at 16:37, Hugo Salgado <[email protected]> wrote: > > > > Dear Atlas team. > > I have a script to launch a new measurement using an old measurement > > list of probes ids, using type:msm. This script worked ok several > > times (last time like 1 month ago), but now it gives me the error: > > > > {"error":{"detail":"There was a problem with your > > request","status":400,"title":"Bad > > Request","code":102,"errors":[{"source":{"pointer":"/probes/0/value"},"detail":"The > > measurement you selected for your probe request does not exist"}]}} > > > > However I still can see the old measurement on the web page! > > > > I solved it downloading the list of probes using a GET to > > > > https://atlas.ripe.net/api/v2/measurements//<OLD_MEASUREMENT_ID>?fields=probes' > > and then giving the complete probes list to my script. > > > > Is there any recent change with the type:msm call? > > > > Thanks, > > > > Hugo > > >
signature.asc
Description: PGP signature
