mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #4330] [Bug]: Offboarding Wizard always schedules for now #1959
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1959
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DaRacci on GitHub (Jun 23, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4330
Required confirmations before submitting
Issue Description
When making an scheduled Offboarding using the Wizard despite adding a scheduled date and that being visible in the task parameters of the scheduled task when added to the scheduler its added at the current time.
I've ensured that my CIPP & CIPP-API are up to date, I've restarted the CIPP-API function but this still persists.
Adding a Job to the scheduler manually using the "Add Job" button works correctly.
The API Response for one of these tasks is as follows:
Environment Type
Non-sponsored user
Front End Version
v8.1.0
Back End Version
v8.1.0
Relevant Logs / Stack Trace
@github-actions[bot] commented on GitHub (Jun 23, 2025):
Thank you for reporting a potential bug. If you would like to work on this bug, please comment:
Thank you for helping us maintain the project!
@TallgeeseVIII commented on GitHub (Jun 23, 2025):
Same issue occurring on my end.
My colleague scheduled an offboarding but it occurred immediately.
@JohnDuprey commented on GitHub (Jul 1, 2025):
This should be resolved in 8.1.1