Issue with time zone(s)

Hello, I’ve been using your plugin for a few days and may have noticed an issue regarding time zones. First of all, these are my settings regarding the Timezone set in WordPress: Universal time is 2021-08-31 18:03:34. Local time is 2021-08-31 20:03:34. I’ve created a form entry on 2021-08-31 17:50:00 local time. Your plugin is set to delete entries that are older than 10 minutes and runs every 1 hour . My understanding is that the entry should’ve been deleted around 2021-08-31 18:00:00 local time. This, however, wasn’t the case. The entry got deleted two hours later, on 2021-08-31 20:00:00 local time. When having a look at the log output, one can see that there is an offset of 2 hours from universal time to local time, likely causing issues. The form in question is form #4 . 2021-08-31 19:00:03.908513 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Search criteria for form #4: Array ( [start_date] => 1970-01-01 00:00:00 [end_date] => 2021-08-31 16:50:03 [payment_status] => ) 2021-08-31 19:00:03.910904 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Not deleting entries for form #4 because no entries were found matching the search criteria. 2021-08-31 19:20:02.842380 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #1 because it is not due to be run yet. 2021-08-31 19:20:02.854918 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #2 because it is not due to be run yet. 2021-08-31 19:20:02.860824 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #3 because it is not due to be run yet. 2021-08-31 19:20:02.862658 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #4 because it is not due to be run yet. 2021-08-31 19:30:03.092097 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #1 because it is not due to be run yet. 2021-08-31 19:30:03.093286 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #2 because it is not due to be run yet. 2021-08-31 19:30:03.094397 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #3 because it is not due to be run yet. 2021-08-31 19:30:03.095495 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #4 because it is not due to be run yet. 2021-08-31 19:50:02.826430 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #1 because it is not due to be run yet. 2021-08-31 19:50:02.831048 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #2 because it is not due to be run yet. 2021-08-31 19:50:02.834055 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #3 because it is not due to be run yet. 2021-08-31 19:50:02.835810 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Skipping deletion for form #4 because it is not due to be run yet. [...] 2021-08-31 20:00:02.601553 - DEBUG --> GF_Entry_Expiration::maybe_run_deletion(): Search criteria for form #4: Array ( [start_date] => 1970-01-01 00:00:00 [end_date] => 2021-08-31 17:50:02 [payment_status] => ) 2021-08-31 20:00:02.608485 - DEBUG --> GF_Entry_Expiration::delete_form_entries(): Starting deletion of page 1 of 0 2021-08-31 20:00:02.714235 - DEBUG --> GF_Entry_Expiration::delete_form_entries(): Deletion completed. Could you please have a look at this issue? Thank you very much in advance. This topic was modified 4 years, 9 months ago by austrianuser . This topic was modified 4 years, 9 months ago by austrianuser . Hey @austrianuser , Could you please reach out to us via our contact form about this? I’d like to send you a test build with a potential fix. Thanks! Thanks to @austrianuser ’s help with testing a potential fix, an update has been released that resolves this issue.