This article is only relevant if you're using the official SAS CI integration for Agillic.
The SAS CI integration allows you to set up and execute a Flow created in SAS CI and have the execution trigger send-outs.
When this execution occurs, SAS CI auto-generates a Flow in Agillic and executes it for a list of recipients from SAS CI. As it's a different execution model, troubleshooting is only slightly different than for a Flow manually created in Agillic.
How to Investigate a Failed Execution
If an execution didn't seem to send out as expected, despite a successful message in SAS CI, the first Step is to have a look at the Flow and import file.
The name of your SAS Flow is based on:
- The name 'SAS'.
- The name of the outbound communication.
- The type of the outbound communication, such as email.
- The execution priority, such as 'Normal'.
- The ID of the Flow, such as '1234'.
- Subject line test settings, if enabled on the email.
An example of a SAS CI generated Flow with a subject line test on 20% for 4 hours would be:
SAS-NS 046 ice cream-email-NORMAL-1234-SLT-20-4-BEST_OPEN
Because of this formula, changing the name of an outbound communication or the settings for the subject line test will cause Agillic to auto-generate a new Flow.
How to Investigate a SAS CI Generated Flow
To investigate a SAS CI generated Flow, you need to:
- Search for the Flow based on the name of the outbound communication.
- Open the Flow. If the Flow does not exist, please contact Agillic Support.
- Open the 'Log' panel for the Flow.
- If an execution recently happened for the expected number of recipients.
- If the log shows the expected execution.
- If the log doesn't show the expected execution, you should investigate the import file.
- Investigate the Flow with a recipient from the SAS CI generated list. Agillic will attempt to reuse a previously generated Flow if available, assuming the email Step contains the same email, and the email is configured with identical settings.
How to Investigate the Import File
Like any import file, the files from SAS CI appear in the import log. Investigate the import log to locate the specific import file.
The name of the import file is based on:
- The name 'CAMP'.
- The camp number from SAS CI.
- The name '_COMM'.
- The comm number from SAS CI.
An example of a SAS CI generated import file would be:
In order to investigate the Import File, you need to:
- Locate the correct import file for your execution.
- Verify if the import file was correctly imported. If the import file was imported correctly, please contact Agillic Support for further assistance.
- Look at the error codes for the import file.
- Correct the data in SAS CI based on the errors and attempt a new execution.
In case the error codes from the import log don't provide enough insight into the issue, you can use the WebDAV connection to download and look at the raw import file. You can learn more about how to set up the WebDAV connection here.