Pipelined fails with error “No task corresponds to the mask pipelined@< instance >”
Your version of Adobe Campaign Classic does not support the pipeline.
- Check if the pipelined element is present in the config file. If not, it means it’s not supported.
- Upgrade to Campaign 20.3 or Gold Standard 11.
Pipelined fails with ‘’ aurait dû commencer par
The NmsPipeline_Config option is not set. It’s actually a JSON parsing error.
Set the JSON config in the option NmsPipeline_Config. See “routing option” in this page.
Pipelined fails with “the subject must be a valid organization or client”
The Organization identifier configuration is not valid.
- Check that the IMSOrgId is set in the serverConf.xml.
- Look for an empty IMSOrgId in the instance config file that can override the default. If so, remove it.
- Check that the IMSOrgId matches that of the customer in the Experience Cloud.
Pipelined fails with “invalid key”
The @authPrivateKey parameter of the instance config file is incorrect.
- Check that the authPrivateKey is set.
- Check that the authPrivateKey: starts with @, ends with =, and is about 4000 characters long.
- Look for the original key and check that it is: in RSA format, 4096 bits long, and starts with -----BEGIN RSA PRIVATE KEY-----.
If necessary, re-create the key and register it on Adobe Analytics.
- Check that the key was encoded within the same instance as pipelined.
Pipelined fails with “unable to read the token during authentication”
The private key has an invalid format.
- Run the steps for key encryption on this page.
- Check that the key is encrypted on the same instance.
- Check that the authPrivateKey in the config file matches the generated key.
Make sure to use OpenSSL to generate the key pair. PuttyGen for example, does not generate the proper format.
No triggers are retrieved
When the pipelined process is running and no triggers are retrieved:
- Make sure that the trigger is active in Analytics and is generating events.
- Make sure that the pipelined process is running.
- Look for errors in the pipelined log.
- Look for errors in the pipelined status page. trigger-discarted, trigger-failures should be zero.
- Check that the trigger name is configured in the NmsPipeline_Config option. If there is a doubt, use the wildcard option.
- Check that Analytics has an active trigger and is generating events. There could be a delay of a few hours after the configuration is made in Analytics before it’s active.
Events are not linked to a customer
When some events are not linked to a customer:
- Check that the reconciliation workflow is running, if applicable.
- Check that the event contains a customer ID.
- Make a query on the customer table using the customer ID.
- Check the frequency of the customer import. New customers are imported into Adobe Campaign with a workflow.
Latency in events processing
When the Analytics timestamp is much older than the creation date of the event in Campaign.
Generally, a trigger can take 15-90 minutes to launch a marketing campaign. This varies depending on the implementation of data collection, load on the pipeline, custom configuration of the defined trigger, and the workflow in Adobe Campaign.
- Check if the pipelined process has been running.
- Look for errors in pipelined.log that can cause retries. Fix the errors, if applicable.
- Check the pipelined status page for the queue size. If the queue size is large, improve the performance of the JS.
- Since a delay seems to increase with volume, configure the triggers on Analytics using fewer messages.
Upgrading stage instances from legacy authentication to Adobe IO authentication
Changing the integration authentication on your stage instance will not affect the configuration of your production instance. You can choose to upgrade your stage instance then update the authentication to Adobe IO and test your triggers on your stage instance.
Your production instance will continue to use the legacy authentication and will be unaffected by this change.