Killing User Sessions with a Function

[JasonMcD (Jason McDermott)]

I like kicking out all users every night. Technically “inactive” ones, but at 11PM, that’s basically all of them. It just feels right.

Anyway, I made an EFx to do this back in May (2024), and scheduled it with a Flow (Power Automate) to run at 10:58 PM each night.

Well, it always said it there were no sessions to kill, so I just assumed the data looked different at night, and never came back to it till today.

Looks like I blamed the wrong thing. I think the EFx was fine; it’s the Flow that fails.

I made a separate EFx just to show me active and inactive users. They are nonzero in Production as shown in Postman:

Now here is that same EFx in Power Automate (also Production) - all zeroes! And status is 200 OK.

So did I just mess up the Flow? Or is there something else going on here?

Anyway, I don’t know why I didn’t just schedule the deletion EFx in Epicor (instead of a Flow), but I did now and I’ll see what happens tonight.

For some fun background reading:

Anyone ever done a where-clause on SessionAdmin.GetList?

If not, it’s fine. I’m just asking. It looks like I can use GetFilteredSessionList which is bizarre but what I need. (The filter of 2 = inactive users.) But for the sake of argument, what is the syntax for the whereClause here? I’m used to it being SQL syntax (wrapped in double quotes). So I expected to do "InUse = 0" But that did not work, nor anything else I tried. Nothing caused it to fail, but nothing filtered the results either. [image] Voice from the future TL;DR 1: The where claus…

[mbayley (Michael Bayley)]

Is the user the request being sent as also Security Manager in Power Automate?

[JasonMcD (Jason McDermott)]

Ah. No it is not.

Yes in Postman, No in PA.

I bet that’s it.

[mbayley (Michael Bayley)]

You might need Global Security Manager - not sure

[JasonMcD (Jason McDermott)]

@mbayley

Security Manager in Power Automate

That’s it!

I knew you were right as soon as you said it. Creating a new user also has the same restriction in REST. But since that’s the only time I’ve ever encountered the restriction, I just forgot all about that possibility.

[JasonMcD (Jason McDermott)]

@JasonMcD

Anyway, I don’t know why I didn’t just schedule the deletion EFx in Epicor (instead of a Flow), but I did now and I’ll see what happens tonight.

Post script

Good news: Flow worked perfectly last night and deleted 88 inactive user sessions! Huzzah @mbayley !

Odd news: The scheduling of the Function (inside Kinetic) failed. I have not investigated; probably some obvious mistake I made. I just wanted to say that it’s ironic that the Flow worked better than native Epicor scheduling.

FYI, the scheduled EFx (not the Flow) was a fallback. Flow ran at 10:55; this ran at 10:58. Maybe it bombed because there were no sessions to delete. But it’s a moot point. I can fix the issue (or not) in time.