Hi Malte:

  Yes, it was the time designation that caused the confusion! In my code, I initially wrote:

  However, when I stepped through the debugging process, I encountered an error indicating that the measurement start time must be in the future. To resolve this, I added a random delay to the start time:

start_time=datetime.utcnow() + timedelta(random.randint(0, 1)),

  I assumed that the unit of the timedelta parameter was seconds, but it turns out it is actually in days. Apologies for the mistake and the bothering I made.

  Thank you all for your kind help!

Best regards,

Sun

-----Original Messages-----
From: "Malte Tashiro via ripe-atlas" <ripe-atlas@ripe.net>
Send time: Friday, 12/20/2024 10:51:57
To: 孙乐童 <slt20@mails.tsinghua.edu.cn>
Cc: ripe-atlas@ripe.net
Subject: [atlas] Re: Why measurements using api are apt to fail while those using web interface can usually succeed?

Hi Sun,

I've looked at the measurements when you sent your mail and at least at that
time the measurements you've scheduled via the API were set to start in the
future. In that case they show up in the UI as "Specified" until the scheduled
start time.

Not sure if that was intentional, but maybe cousteau handles timestamps
differently than you think (e.g., assumes UTC instead of local time)?

Just a guess.

Best,
Malte

-----
To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. 
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/