REST API Actions don't always show up in the console

Content Authoring
1

Hi,

We’re running some REST API calls so we can create actions targeted for individual workstations. (Ex. USB Exception, ScreenSaver exception). These actions are using existing fixlet, and we just update the targetid of the machine. The actions are created successful, we get actionID returned from the RestAPI call.

Question? For some reason these actions are not visible in the console? Even after waiting for 10-20 minutes or longer.

I’m able to run simple REST API query to retrieve actionID, Name

((id of it), (name of it)) of bes actions whose ( name of it starts with "PC1-UTL - ADD" And name of it contains "ComputerName")

Querying SQL Table dbo.actions (I know not recommended but only for testing purpose), I can see the actions also

Any reason why these would not showup in the console. It’s not consistent, but I would say more annoying than anything. It’s not permission issue as I’m able to see also actions created by the same api account in same BigFix Site.

The actions also complete fine on the workstation.

We currently have around 2,000 actions in our environment, we have some clean-up scripts to delete stopped/expired actions every day, and we have seen increase in the #actions has been around 2000 for last few months

Thx!

2

Just log in with a Master Operator account and see if the action is visible there, rather than logging in with an NMO (Non-Master Operator).

Checking this will clear up the issue right away!

3

There could be multiple possible causes:

  1. Although you mentioned that permissions are not the issue, it is still worth validating as a first step what @shabircse suggested.

  2. Verify Console filters for actions.

  3. Monitor FillDB performance and resource utilization to determine.

  4. Verify the Console refresh interval. If it is configured to refresh every 10–20 minutes.

  5. Check for concurrent REST API jobs or SQL Server maintenance activities (example: index reorganizations, backups, or other long-running database tasks) that could temporarily delay database updates or Console visibility.

4

When one non-master-operator (you), is viewing actions taken by another operator (the API account), the Console doesn't show you all of the actions taken by the other operator - you are filtered down so you can only see the actions the other operator took, that effects one of the Computers on which your own account has operator rights.

To do that, you only see the action result after at least one of your own managed computers reports back a result for the action.

If the API action targeted a computer that is offline, unreachable over the network, or is otherwise delayed in reporting back a result for the action -- then your operator account won't see that the action exists.