# Workflow in SailPoint IDN stopped revoking access for deactivated accounts, except roles – Anyone else experiencing this issue? **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** workflows, sailpoint-identity-security\ **Created:** [October 9, 2024, 12:24am UTC](https://developer.sailpoint.com/discuss/t/workflow-in-sailpoint-idn-stopped-revoking-access-for-deactivated-accounts-except-roles-anyone-else-experiencing-this-issue/84425 "2024-10-09T00:24:57Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![dominick-miller](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/dominick-miller/32/29002_2.png) [@dominick-miller](https://developer.sailpoint.com/discuss/u/dominick-miller)\ **Post date:** [October 9, 2024, 3:55pm UTC](https://developer.sailpoint.com/discuss/t/workflow-in-sailpoint-idn-stopped-revoking-access-for-deactivated-accounts-except-roles-anyone-else-experiencing-this-issue/84425/2 "2024-10-09T15:55:54Z")
Hey @clebercarvalhoRaise : I am getting this same “unexpected end of JSON input” error in a workflow that was previously working. I have spent 5+ hours debugging and cannot understand what the issue is. My guess is that SailPoint recently pushed a Workflow update and didn’t validate fully but my guess is as good as yours. For reference, I opened a similar post here: [Unable to use loop input or loop context in loop steps - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community](https://developer.sailpoint.com/discuss/t/unable-to-use-loop-input-or-loop-context-in-loop-steps/84404) I think the bug lies exclusively with passing loop input and loop context variables to inner loop HTTP operations, as I am still able to call Get Identity inside the loop, for example. --- _[View the full topic](https://developer.sailpoint.com/discuss/t/workflow-in-sailpoint-idn-stopped-revoking-access-for-deactivated-accounts-except-roles-anyone-else-experiencing-this-issue/84425)._