Configuration Status Block

This means your J1 Web server’s URL cannot be found on the internet.

Ensure a valid SSL certificate is installed on the J1 Web server and then verify the URL entered on the J1 Web, System Administration, Product Installs and Sign In page in the J1 Web URL field has https: selected.

If you update the URL, you will need to unassign and reassign users to their Twilio phone numbers. This resyncs Twilio to the right address. You will also need ensure HTTPS traffic can make it through your firewall to your J1 Web server.

This indicates the API key and/or the Validation API key are no longer valid. This can happen if the keys are removed/expired in the SendGrid dashboard or if the incorrect key was entered in System Administration, System Settings, Communications, Email Provider section.

To correct the issue, generate new keys in the SendGrid Dashboard and re-enter them into J1 Web. For more information, see Email Provider Setup.

SendGrid article on domain authentication: https://docs.sendgrid.com/api-reference/domain-authentication/list-all-authenticated-domains

This indicates the URL being used for Inbound Parse in SendGrid does not match the URL in J1 Web, System Administration, System Settings, Product Installs and Sign In. This can happen if the URL was updated in J1 Web after Communications was set up to work with SendGrid.

To resolve the issue, verify the URL in Product Installs and Sign In is correct and re-validate your Email Provider Settings in System Administration, Communications, Email Provider configurations.

One way to confirm your MX record is to look at the SendGrid Inbound Parse logs. From SendGrid, access Stats & Parse Webhook and a test attempt chart appears. If you see attempts were made, your MX record is properly configured and you need to log a call with SendGrid to troubleshoot. Sample chart shown below:

If you do not see attempts were made, configure your DNS for your inbound subdomain using these steps:

This message indicates the URL being used for Mail Settings Event Webhook in SendGrid does not match the URL in J1 Web, System Administration, System Settings, Product Installs and Sign In. This can happen if the URL was updated in J1 Web after Communications was set up to work with SendGrid.

To resolve the issue, ensure the URL in Product Installs and Sign In is correct and re-validate your Email Provider Settings in System Administration, Communications, Email Provider configurations.

This indicates the Account SID and/or the Authentication token provided are no longer valid. This can happen if the keys are removed/expired in the Twilio Console or if the incorrect keys were entered in System Administration, Communications, Text Provider configurations.

To resolve the issue, generate new keys in Twilio and re-enter them into J1 Web.

This indicates the URL being used for Messaging Webhooks for one or more of your phone numbers in Twilio does not match the URL in J1 Web, System Administration, System Settings, Product Installs and Sign In. This can happen if the URL was updated in J1 Web after Communications has been setup to work with Twilio.

To resolve the issue, ensure the URL in Product Installs and Sign In is correct and re-assign users to the phone number to force the URL to update in Twilio.

This indicates one or more of your Data Merge Options data sets are considered complex. This means they search data based on several parameters and the system cannot append a WHERE clause. Without the WHERE clause, the server cannot reduce the amount of information being returned which can lead to performance issues and cause your communications to not be delivered when expected.

Check your Data Merge Options data sets to ensure they include a WHERE clause.