Skip to content

[pull] master from KelvinTegelaar:master#1

Merged
pull[bot] merged 40 commits intotmabaker:masterfrom
KelvinTegelaar:master
Mar 10, 2024
Merged

[pull] master from KelvinTegelaar:master#1
pull[bot] merged 40 commits intotmabaker:masterfrom
KelvinTegelaar:master

Conversation

@pull
Copy link
Copy Markdown

@pull pull bot commented Mar 10, 2024

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

BNWEIN and others added 30 commits November 21, 2023 08:40
[pull] dev from KelvinTegelaar:dev
[pull] dev from KelvinTegelaar:dev
[pull] dev from KelvinTegelaar:dev
[pull] dev from KelvinTegelaar:dev
[pull] dev from KelvinTegelaar:dev
added DKIM Records to table and export
Added custom thresholds for SharePoint and Mailbox Quota alerts
Added custom thresholds for SharePoint and Mailbox Quota alerts
Tweak ExecScheduledCommand
allow for json input for larger depth
[pull] dev from KelvinTegelaar:dev
@pull pull bot added the ⤵️ pull label Mar 10, 2024
@pull pull bot merged commit cc02a26 into tmabaker:master Mar 10, 2024
pull bot pushed a commit that referenced this pull request Jan 10, 2025
pull bot pushed a commit that referenced this pull request May 28, 2025
[pull] dev from KelvinTegelaar:dev
pull bot pushed a commit that referenced this pull request Mar 13, 2026
…state

Two bugs caused scheduled offboarding tasks to silently disappear:

1. In Push-ExecScheduledCommand, if Invoke-CIPPOffboardingJob threw an
   exception the inner catch set $State='Failed', but the outer state
   update unconditionally set TaskState='Processing' for all orchestrator-
   based commands, ignoring the failure. The task was then stuck in
   'Processing' showing "Orchestration in progress" with no way to recover.
   Fixed by checking $State before deciding between 'Processing' and 'Failed'.

2. In Start-UserTasksOrchestrator the recovery filter included stuck
   'Pending' (>24h) and 'Running' (>4h) tasks but omitted 'Processing'.
   Any task stuck in 'Processing' (from bug #1 or from an orchestration
   where the post-execution handler itself failed) would never be retried.
   Fixed by adding 'Processing' to the recovery filter with the same
   4-hour timeout used for 'Running'.

https://claude.ai/code/session_019TANRi9wms5e5W1nJgZWQm
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants