Check the obvious causes first
- Is the reference in the email? Arkata reads the reference out of the subject line or the PDF. If your submission did not carry one, there is nothing to match on.
- Does the reference on the project match? Compare the internal reference in the correspondence with the one on the project. A changed internal reference stops matching immediately.
- Is the PA reference recorded? Several email types match on it, and it is the only thing some of them can use.
- Is it one of the eight supported types? Anything else is flagged by design. See Supported email scenarios.
Which reference each email needs
Different authority emails carry different references, so what is missing depends on the type.Non-executable decision notices carry no internal reference at all, so the PA reference must be recorded on the project before one can be filed.
Handle a flagged email
Nothing is lost when an email is flagged. Deal with it the way you would have before: open the email, download the attachment and upload it to the project yourself, then create a task if the email needs an action. Then fix the cause so the next one files on its own: record the PA reference on the project, or start quoting the internal reference in your submissions.Stop it happening again
Next steps
Project references
Setting and changing both references.
Supported email scenarios
Which emails Arkata can file.