You are currently reviewing an older revision of this page.
After a change to the site domain or the creation of a custom email sender, users are reporting emails from Appian are not being delivered within a timely manner to their company issued email address.
Both of these changes allow Appian to send emails under a customer owned domain. Oftentimes, these changes also require you to update the SPF record for your domain to include the Appian SPF record.
To address this issue, please do the following:
nslookup -type='txt' <FULL_SITE_FQDN>
include
This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:
If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.
Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.
If there is no action or workaround that resolves the issue, use the following language:
This section is optional and should only be used as an alternative action if there is a massive technical debt associated with performing the action in the above section for customers (such as upgrading). It can also be used if there is a solution to the issue in the article but is more inconvenient to implement or it causes other undesirable behavior and wouldn’t warrant being an action.
This article applies to all versions of Appian.
Last Reviewed: Month YYYY