How can we help?

Account Monitor

Overview

Cordial's Account Monitor provides you with key information on errors and warnings, empowering you to resolve those issues quickly and efficiently.

The Account Monitoring dashboard:

  • Provides insight into issues that might otherwise be missed in a job processing millions of records.
  • Provides real-time detailed information that you can address immediately.

Access the Account Monitor

Click the Account Monitoring icon at the top of the Cordial dashboard to access your Account Monitoring dashboard (also known as the client logging dashboard).

Filter jobs

Available at the top of the Account Monitoring dashboard, you can filter jobs according to the following categories:

  • Filter by level: Error or Warning
  • Filter by category based on their functional area of the platform: Imports, Messaging, JS Listener, Jobs
  • Search for logs most commonly by message ID, job ID, or error message. You can also search on strings within the message and any additional text present in the log data.

Timeline

The interactive timeline on the Account Monitoring dashboard displays the last three days of logs filtered down to the minute. You can click an issue bar to get additional information.

Click the Info icon to view warnings and errors.

Issue details

You can click any log at the bottom of the Account Monitoring dashboard to access the Issue Details pane. The issue details pane includes information specific to each issue.

  • Select JSON to view the details as a JSON object.

Aggregation

There are options to aggregate log information for the messaging, jobs, and imports categories. When one of these categories is selected, the option to Aggregate by will appear in the logs section below the timeline.

Aggregate by message ID:

 

Common errors

Below you'll find common errors that surface in the Account Monitoring dashboard.

Messaging

Log message Error description Suggested solution

Unable to send email message because rendered subject is empty.

Message didn’t fully go out because of empty subject lines.

Review the logic being used to generate your subject line. Account for potentially empty values that may be generated and supply a default.

Smarty compilation error. (specific error)

Smarty direct write utility.

Check your Smarty for syntax errors.

Smarty compilation error. (specific error)

Smarty utility errors: failed to shorten link.

Check your Smarty for syntax errors.

Smarty compilation error. (specific error)

Unable to load template.

Ensure that the referenced template exists.

Ensure there are no smarty errors in the referenced template.

Smarty compilation error. (specific error)

Generic Smarty syntax error.

Check your Smarty for syntax errors.

Smarty compilation error. (specific error)

$in needs an array error.

This is commonly a result of dynamically building queries for smarty utilities. (e.g. getSupplementRecords where the variable used for an 'in' clause in the query didn't contain an array.)

Smarty utility errors, JSON cannot be decoded.

Invalid JSON has been detected.

Check the data being returned by your source to ensure the JSON is valid. 

Smarty utility errors, XML cannot be decoded.

Invalid XML has been detected.

Check the data being returned by your source to ensure the XML is valid. 

Max tracked links limit (500) is reached.

Max number of tracked links (500) in an email message has been exceeded.

Ensure that you are not tracking more than 500 distinct links in your message. 

Ensure you are not passing dynamic smarty values to data-crdl-key which can result in a unique tracked link per contact. 

Utility function errors, external endpoint error 404/missing/error.

Smarty utility errors: external endpoint error 404/missing (failed getJson/getXML/getRaw).

Check to see that your source is reachable. 

Nested experiments are not supported.

Experiments within experiments are not supported. 

Check to see if experiments in your message have been nested. Check whether the inclusion of HTML content may have inadvertently introduced an experiment within another experiment. 

Imports

Log message Error description Suggested solution
Unable to import products due to (specific error)

Unable to retrieve file for product imports.

Check the connection to the file.

Check that the file exists. 

Check that the file is of an accepted format. 

Check your request body (if importing via the API).

Unable to import orders due to (specific error)

Unable to retrieve file for orders imports.

Check the connection to the file.

Check that the file exists. 

Check that the file is of an accepted format. 

Check your request body (if importing via the API).

Unable to import supplements due to (specific error)

Unable to retrieve file for supplements imports.

Check the connection to the file.

Check that the file exists. 

Check that the file is of an accepted format. 

Check your request body (if importing via the API).

Unable to import Sculpt blocks due to (specific error) Unable to retrieve file for Sculpt blocks imports.

Check the connection to the file.

Check that the file exists. 

Check that the file is of an accepted format. 

Check your request body (if importing via the API).

Unable to import sculpt templates due to (specific error) Unable to retrieve file for Sculpt templates imports.

Check the connection to the file.

Check that the file exists. 

Check that the file is of an accepted format. 

Check your request body (if importing via the API).

  Connection issue. Check your connection information.
  File could not be found. Check that your file exists in your specified path.

JavaScript (JS) Listener

Log message Error description Suggested solution
JS Listener upsert contact error

Contact could not inserted due to validation error.

Ensure the JS Listener is correctly implemented.

Ensure you are passing required attributes.

Check validation rules on attributes to ensure they are being adhered to (ex. max number limit)

JS Listener upsert contact error. Key is not part of the schema for this resource. Ensure that the contact attributes being passed by your javascript are valid contact attributes defined in your account
Tracking request isn't using vanity domain.

Client sends reqs to track.cordial.ioinstead of using vanity domain.

Update your trackUrl path in the JS Listener implementation.

 

Comments

0 comments

Please sign in to leave a comment.