Work outwards. Most missing bubbles are settled on the machine in front of you, and the ones that are not usually show up as the same complaint across every workstation at once.

On the workstation

• Permissions and admin rights. Fetchit and its service have to run with administrative privileges. Without them the application may not function correctly, and clicking a bubble may fail to reach the PMS.
• Version mismatch. Running different versions of Fetchit on the server and the workstations causes incompatibility. Every machine in a clinic should be on the same version.
• Partial installs. A half-finished install, or a mix of versions inside one clinic, makes bubbles either not appear or misbehave.
• Legacy version conflicts. Both the legacy and the current version installed, or remnants of a previous install left behind, conflict with each other. Legacy versions read their configuration from the registry, which can interfere with the current one.
• System tray visibility. If Fetchit is not in the system tray, or the icon reports "Fetchit is already running" without showing bubbles, the application itself is in a bad state.
• Recent reboots. A machine that has just rebooted, or a server rebooted over a weekend, can leave the service down and the clinic without bubbles.

In the configuration

• Incorrect configuration paths. A wrong path to the PMS, such as an AVImark folder with the wrong slash character or a trailing character, stops bubbles appearing.
• Service configuration. Missing or wrong settings in the Fetchit Service Configurator produce no bubbles at all. Check every field, including the case-sensitive Impromed names.
• Misconfigured services. Wrong settings on one machine, a popup style for the wrong PMS for example, make bubbles behave differently there than everywhere else.
• API key and configuration errors. The right API key and settings have to be entered during setup. In ClearVoice specifically, the Schultz Technology API key option must be ticked for the Fetchit user, or no call events arrive.

The service and the database

• The Fetchit service is not running. It has to be running on the server and on the workstations. If it is not, or it is not set to restart automatically, bubbles either stop or arrive red instead of blue.
• SQL Server issues. The FISQL service must be running and connected. A dropped connection that fails to reopen takes the bubbles with it.
• Database connection issues. The database server has to be configured and reachable. An error in the SQL Server installation or configuration stops Fetchit displaying anything.
• Client data sync issues. When the sync between Fetchit and the PMS is failing, bubbles either do not appear or show the wrong information.

The phone system

• API dispatch failures. The provider API, CoreDial for example, may not be dispatching call information. Without that data there is nothing to raise a bubble for.
• API server problems. The CoreDial API server that dispatches call events can itself fail, which needs a restart on their side or a longer-term fix.
• Incorrect CallerID box setup. A clinic that has changed phone systems, from analog to VoIP for example, needs the CallerID box reconfigured for the new one.

The network and our platform

• Network problems. Latency, firewalls and antivirus tools can all keep call data from reaching Fetchit.
• Network layer degradation. A performance problem in the network layer delays or drops bubbles. This is not about load; the layer itself misbehaves.
• SSL certificate expiry. A certificate that expires without auto-renewing stops Fetchit connecting out at all.
• Azure cloud misbehaviour. A server in Azure intermittently refusing to respond leaves some customers without bubbles some of the time.
• Memory pressure in Azure Kubernetes Service. Memory problems in AKS can stop bubbles being delivered until it recovers.

The client's data

• Inactive accounts. An inactive account may not show bubbles for its incoming calls.
• Misconfigured client systems. Some systems are set up wrongly enough that bubbles do not come up, or the system does not recognise certain clients.
• Bubbles that do not act. A bubble that appears but does not open the right record, disappears when clicked, or reports something like "Avimark is not running" is an integration problem rather than a delivery one.
• Demo environments. Demo setups produce their own version of all of this, usually from out-of-date configuration.

Performance

Sometimes the bubble is not missing, just late. A noticeable lag between the call arriving and the client information appearing on screen reads to a clinic as a bubble that never came. Check the phone worker and the network before you go looking for a configuration fault.