The connection to TouchPoint can't be made because the plugin has not been fully configured in WordPress. This is probably because a username or password haven't been set for connecting to TouchPoint. The WordPress admin will need to go to the WordPress dashboard, then Settings > TouchPoint-WP to configure the settings.

The connection to TouchPoint can't be made because the plugin has not been fully configured in WordPress. This is probably because the TouchPoint hostname (e.g. mychurch.tpsdb.com) hasn't been configured. The WordPress admin will need to go to the WordPress dashboard, then Settings > TouchPoint-WP to configure the settings.

One of the background processes that cleans up stale data encountered an issue. The specific issue will depend on the message.

The automated process to update a script on the TouchPoint server. Go to the TouchPoint-WP settings within WordPress and generate and deploy the settings.

Data extracted from the database didn't match the expected type. This issue should have been gracefully handled in the background, and should disappear permanently by revisiting and re-saving the plugin's settings.

More than one post exist with the same Post Type and TouchPoint ID. This is extremely unlikely. If you encounter this condition, let the developers know.

More than one post exist with the same Post Type and TouchPoint ID. This happens sometimes, but can usually be corrected automatically.

Sometimes large images, or plugins that handle images, can cause the import process to timeout. This error appears if this seems to have happened recently. Image updates are disabled until this issue is resolved. Get in touch with the plugin developers for help troubleshooting this issue.

TouchPoint is imposing rate limiting because it has received an unusually high number of requests. This will likely pass in a few moments.

The syncing agent could not find or create a post for the involvement. The reason is unknown, but it's likely because of a problem connecting to the database.

The TouchPoint-WP API was asked to find an Involvement with an invalid Involvement ID. A valid Involvement ID is required.

The TouchPoint-WP API was asked to find a Meeting with an invalid Meeting ID. A valid Meeting ID is required.

This is most likely caused with a conflict with another plugin that is attempting to set the display date/time field for posts. Since Partners that space to provide notable attributes rather than actual dates, this poses a conflict.

TouchPoint Reports must include a name.

Invalid Report type. Currently, only SQL reports are supported.

The syncing agent could not create a post for the Report. The reason is unknown, but it's likely because of a problem connecting to the database.

The authentication tool can be used, within a single script, for authenticating the user to multiple domains. But, those domains much each have a valid API key in the TouchPoint settings.

The token passed between TouchPoint and WordPress expired. This will happen if the internet connection was lost during the login process. Try again.

The token passed between TouchPoint and WordPress either has been used before, or has otherwise been invalidated. Try logging in again.

The token passed between TouchPoint and WordPress either has been used before, or has otherwise been invalidated. Try logging in again.

The secret key used between TouchPoint and WordPress is invalid.

The user session was not initialized correctly and therefore can't be used.

The TouchPoint user's information has successfully been passed to WordPress, but there is no matching user in WordPress and automatic user provisioning is not enabled. Enable automatic provisioning and this message should go away forever.

An error was reported by the IP geolocation service. The error and its conditions may vary by situation.

An error was reported by a geolocation service. The error and its conditions may vary by situation.

The services could not geolocate the user. This is noteworthy because of where the failure occurred in the process.

The geolocation services returned an invalid response.

Most likely, TouchPoint is down.

Something went wrong with TouchPoint's execution of the API script. This is consistently a TouchPoint server problem and should be reported to TouchPoint support.

Something went wrong in calling the API. This should be reported to the TouchPoint-WP developers.

Something went wrong in calling the API. This is most likely from data changing unexpectedly within TouchPoint.

A Person query in the API failed.