So I noticed that when I was running a Timer containing an API Service that I started getting errors in the RT logs saying that the user-token I was using did not exist. This was odd, since the timer was working fine yesterday and I hadn’t made any changes to it. I then went into the Backendless Pro Manager application to see if restarting the services would fix it, and it came up as seen below and would not show anything under the Server Status dropdown. I had my network admin check the server, and he said that the only thing that occurred were some security updates for the operating system that occurred last night. Screenshots of what I see in Pro Manager and the API service I mentioned are below. Any way to fix this without reverting the server to a backup state? If the security updates really were the cause, we can’t really stop those.
I noticed Mark’s pinned comment and sent this as a message to Staff since this is regarding a Pro installation.