Error Code | Integration | Details/Resolution |
The request to Filogix has timed out | Filogix | Certain deals in Filogix takes longer to respond. If it takes longer than 60 seconds and the connection fails, please contact your Filogix representative. |
Record not found in Velocity | Velocity | If the deal was created in Velocity more than 30 days ago without "Closing Date", the deal cannot be pulled into the CRM. We hope to resolve this in with Velocity in the near future. |
This deal in {Filogix|Velocity} does not belong to a member of your team | Both | If you have requested a deal that is assigned to a broker in Filogix or Velocity, and if that broker is not a user in your CRM, then you will see this message. If you think this is in error, check in with support@bluroot.ca and we will make sure that your team is set up correctly to use the integration. |
BluIntegrate API error (400) | Both | This error code will display for many error types. The message will vary. If you encounter this message, please report this to support@bluroot.ca |
An unexpected response came back from our server | Both | If you encounter this message please report this to support@bluroot.ca |
Error Code | Integration | Details/Resolution |
filter_error | Both | This can be safely ignored. We will remove these in the near future. |
connector_upsert_error | Both | Upserting a record to Zoho threw an error. If your CRM has many customizations, you may require additional integration work to resolve these errors. |
connector_search_error | Both | Something went wrong while searching for records in Zoho. If your CRM has many customizations, you may require additional integration work to resolve these errors. |
connector_lookup_error | Both | Something went wrong while trying to update a record with a lookup field. If your CRM has many customizations, you may require additional integration work to resolve these errors. |