Ok. I am new to using Bigfix so, I didn’t know about the Fixlet Debugger. I could try to use it the next time if I hit something like this again.
I did do a Send Refresh to the endpoint and waited for some time but the status didn’t change in the console. I confirmed in the log on the relay server (the client log - don’t remember it’s name) and it showed that the full status report had been sent.
This is a completely new environment that has been set up. There are no clients/agents installed at this time. It’s just the core infra that has been set up as of now with the Primary, Secondary, Console and Relay.
If this was a cache issue then, how did the status change on its own when I manually uninstalled the relay? Doesn’t seem to be the problem.
It doesn’t sound like any of this was your problem, but here is some explanation:
This would be very rare, but It is technically possible for a client’s report to be dropped if the system got backed up at some point. If the client never sends a full report, it won’t be updated to reflect that. If the client doesn’t get UDP notifications, then it would never get a Send ForceRefresh either. This could cause it to appear not relevant to something in the console.
If you send an action to an endpoint, then it will run it after it gets the UDP notification, polls for commands, or when it reaches it’s gather interval. A client should always eventually run an action, and normally it is immediate. This is why sending an action to a client is a good diagnostic measure.