SparkPost / SparkPost/developers.sparkpost.com

Incorrect "substitution" error hint when domain not fully validated

Open
#380 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
API Blueprint
Stars
18
Forks
9
Avg merge
2d 1h
Merged PRs (30d)
3

Description

Oh no! An Error Occurred
Compliance Pending for Sending Domain [...]

If you notice this happens often, check your substitution data or code syntax as these are frequent causes of preview errors.

The last sentence there doesn't make sense.

image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by searching the documentation source for the quoted substitution-data error hint shown in the issue and review the surrounding preview-error text. Done means the hint accurately reflects the "Compliance Pending for Sending Domain" condition and no longer directs users toward unrelated substitution data or code syntax.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.