Skip to content

[pull] dev from KelvinTegelaar:dev#1

Closed
pull[bot] wants to merge 421 commits intoBeheerIctivity:devfrom
KelvinTegelaar:dev
Closed

[pull] dev from KelvinTegelaar:dev#1
pull[bot] wants to merge 421 commits intoBeheerIctivity:devfrom
KelvinTegelaar:dev

Conversation

@pull
Copy link
Copy Markdown

@pull pull bot commented Aug 19, 2023

See Commits and Changes for more details.


Created by pull[bot]

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

KelvinTegelaar and others added 30 commits July 17, 2023 13:40
[pull] dev from KelvinTegelaar:dev
Resolved issue with Excluded users lists
Changed endpoint to use beta. Occassionally valid conditional access policies were being ignored.
- New function to create GDAP relationship/invite via Graph API
- HTTP & Timer triggers to process relationships activated in last day
- Queue function to map groups to roles following relationship activation
[pull] dev from KelvinTegelaar:dev
ListMFAUsers various bug fixes
@pull pull bot added the ⤵️ pull label Aug 19, 2023
@BeheerIctivity BeheerIctivity deleted the branch BeheerIctivity:dev August 21, 2023 14:38
pull bot added a commit that referenced this pull request Feb 26, 2024
[pull] master from KelvinTegelaar:master
pull bot pushed a commit that referenced this pull request Jan 10, 2025
BeheerIctivity 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