But there is not a header which shows when the job was triggered. It is suggested it can be added a header, for example X-CloudScheduler-Execution-Time which its value (Execution time) could be in any standard like ISO8601 format or Unix time. Also this can be helpful when working with Pub/Sub.
How this should work:
Create a job in Cloud Schedule with any of the possible options.
When the job is triggered, the HTTP request contains in their headers the X-CloudScheduler-Execution-Time. For example, if the Job was triggered on October 9 at 1:10:15 PM CST the header can have the value:
X-CloudScheduler-Execution-Time: 2020-10-09T13:10:15+0000 <-- ISO8601
X-CloudScheduler-Execution-Time: 1602249015 <-- Unix Time
Description
Request summary:
When Cloud Scheduler makes an HTTP request (App Engine HTTP or common HTTP) to an endpoint, the headers in the request are:
But there is not a header which shows when the job was triggered. It is suggested it can be added a header, for example
X-CloudScheduler-Execution-Timewhich its value (Execution time) could be in any standard like ISO8601 format or Unix time. Also this can be helpful when working with Pub/Sub.How this should work:
X-CloudScheduler-Execution-Time. For example, if the Job was triggered on October 9 at 1:10:15 PM CST the header can have the value: