get_variant_schedule always reports next run as UTC (even if schedule is set-up in different time-zone)

[FMKerckhof]

Dear,

While I am aware that the get_variant_schedule is still to be considered experimental, I would like to report a potential bug to help improve it.

Problem description

Currently, if a schedule is set in, for example, GMT+2 (Brussels, CEST), the output of get_variant_schedule(variant)$schedule_data$next_run is reported as: "2022-09-13T14:05:19Z" (i.e. being "Zulu" time or UTC).

Parsing with as.POSIXct leads to the time being recognized as UTC. This is incorrect, since it is actually should read: "2022-09-13T14:05:19+02:00" to be correct (and ISO8601 compliant). Alternatively, the time could be given in UTC as well, but then should be substracted by 2 h (in this case): "2022-09-13T12:05:19Z"

Reprex

Hard to provide a code reprex, since I mostly use the GUI to set a schedule. The following steps should be sufficient to reproduce.

1. Deploy an Rmarkdown document that can generate scheduled output to Rstudio connect
2. Set the schedule in a timezone other than UTC
3. Query the published item using item <- connectapi::content_item
4. Get the item's default variant using default_variant <- connectapi::get_variant_default(item)
5. Get the default variant's schedule using default_schedule <- connectapi::get_variant_schedule(own_default_variant)
6. Inspect the output of default_schedule$schedule_data$next_run

Session information

• R 4.2.1
• RStudio connect 2022.07.0
• connectapi 0.1.1.1

[colearendt]

Thanks for the thorough writeup and reprex here! Apologies for the delay in addressing! This should definitely make it easier to address once we get to it!