From f2badfad9ba7022c32f098eefdc612372de4bcda Mon Sep 17 00:00:00 2001 From: Javier Aliaga Date: Tue, 20 May 2025 10:03:32 +0200 Subject: [PATCH] Update daprdocs/content/en/developing-applications/building-blocks/jobs/jobs-features-concepts.md Co-authored-by: Josh van Leeuwen Signed-off-by: Javier Aliaga --- .../building-blocks/jobs/jobs-features-concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/jobs/jobs-features-concepts.md b/daprdocs/content/en/developing-applications/building-blocks/jobs/jobs-features-concepts.md index 6902af1c3..fbdac273e 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/jobs/jobs-features-concepts.md +++ b/daprdocs/content/en/developing-applications/building-blocks/jobs/jobs-features-concepts.md @@ -114,7 +114,7 @@ POST request to the endpoint `/job/`. The body includes the following or the not-before time from which the schedule should take effect - `Ttl`: An optional value indicating when the job should expire - `Payload`: A collection of bytes containing data originally stored when the job was scheduled -- `Overwrite`: An optional flag to allow the job to overwrite an existing job with the same name +- `Overwrite`: A flag to allow the requested job to overwrite an existing job with the same name, if it already exists. The `DueTime` and `Ttl` fields will reflect an RC3339 timestamp value reflective of the time zone provided when the job was originally scheduled. If no time zone was provided, these values indicate the time zone used by the server running