GlassHive: fixing common sync problems

The GlassHive card and its sync log name every problem in a sentence. Here is what each one means and what to do about it.

GlassHive turned the key down, so Current can read nothing. The key may have been mistyped, removed or replaced in GlassHive. Copy a current key from your GlassHive account and paste it into the GlassHive card. A banner reminds Tenant Admins until it is fixed.

A workspace runs one CRM at a time. While HubSpot is connected, GlassHive cannot be, and the reverse. Open the HubSpot card, disconnect it, then connect GlassHive. What HubSpot already brought into Current stays.

These GlassHive companies matched two or more Current companies by website or name, so Current will not guess. Open the setup, go to Companies, and link each one to the right company, create it as new, or leave it in GlassHive. Until you decide, the company and its contacts are not imported.

GlassHive has no list of its opportunity statuses, so Current learns them as it sees them. A status nobody has mapped yet lands its deals on the first open stage of the GlassHive board. Open the setup, go to Stages, and map each new status to the right stage. Map a status to a won or lost stage to close those deals.

A contact, note, call, meeting or email belongs to a company. When that company is waiting for a decision, was left in GlassHive, or has not been imported yet, Current skips the record and counts it. Decide the company and the skipped records come across on the next run.

Every to-do in Current has an owner. A GlassHive task assigned to a user who is not matched to anyone in your workspace is skipped. Open the setup, go to People, and match that user. The tasks follow on the next run.

GlassHive answered with its rate-limit response. Current stops asking for the rest of that run, waits as long as GlassHive said, and carries on at the next run. Nothing is lost and you do not need to do anything. If it keeps happening, check whether another tool is using the same GlassHive API key at the same time: the limit is shared by everything that uses the key.

Current sent a new record to GlassHive and never got an answer back, so it does not know whether GlassHive created it. To avoid a duplicate, Current does not send it again by itself. For a company or contact, the next run searches GlassHive and links the record if GlassHive did create it. For anything else, look in GlassHive: if the record is missing, create it there.

GlassHive's API can read custom field values but cannot write them. Company and opportunity custom fields you mapped come into Current and update when they change in GlassHive; a change you make to them in Current stays in Current.

Current contacts have no custom fields, so GlassHive's contact custom fields are listed in the setup as staying in GlassHive. The contacts themselves come across with their name, email, phones, title, address and LinkedIn.