Why is JobResponse createdTime always greather than startTime?

Hamilton Tobon Mosquera 1 Reputation point
2021-08-03T20:41:44.69+00:00

I am using Python's Azure IoT SDK for getting information about iot scheduled jobs. According to the docs when a job is created the startTimeUtc and createdTimeUtc are ignored if given. When I create schedule some jobs, wait for them to finish, and get their information using the object IoTHubJobManager with the function get_scheduled_job(job_id), the created_time returned is always greather than the start_time. Sometimes the difference is in the order of minutes, which makes no sense to me.

Please look at the following image: 120257-image.png

Why is this happening? Is it that the created_time means what is contained in the start_time?

Take a look at the docs of JobResponse

Azure IoT SDK
Azure IoT SDK
An Azure software development kit that facilitates building applications that connect to Azure IoT services.
222 questions
{count} votes

1 answer

Sort by: Most helpful
  1. QuantumCache 20,271 Reputation points
    2021-08-26T04:24:22.067+00:00

    Hello @Hamilton Tobon Mosquera Below is the response we received from Microsoft's Product Team on your initial query.

    Job Start Time – user-specified. Could be a future time or some earlier time before the job actually submitted/created.
    Job Create Time – System generated when it receives the request and creates the job to run.

    Job Create Time could be later than the specified job start time if the customer specifies some earlier time as Job start time before sending the job request.

    Please comment in the below section for further discussion.

    If the response is helpful, please click "Accept Answer" and upvote it, so that the other community members can find this question useful.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.