Common output issues and solutions

Listed below are issues and solutions you may encounter in ArcGIS Velocity when writing features from a real-time or big data analytic to various output types. If you encounter an issue not addressed below, work with your administrator to contact Esri Support.

Note:

For issues and solutions related to accessing the Velocity application, signing in, or creating and starting items, see Troubleshooting for general issues and solutions.

Create a New Feature Layer

Send to Kafka

Send to Email

Schema changes when keeping existing features and schema each time the analytic is started

When creating a new Feature Layer output, you must decide whether to keep existing features and schema or replace the features and schema each time the analytic is started.

If you choose to keep existing features and schema each time the analytic is started, the schema of the data sent to this output must remain the same. If you need to change the schema sent to this output, within the analytic, delete the Feature layer (new) output and create a new output.

Schema from data source does not match the schema from the pipeline. Input schema has fields that do not exist in the destination schema.

This message will appear as an error on a Feature layer (new) output if your schema has changed and your feature layer output was configured to keep existing features and schema each time the analytic is started.

This message will appear as a warning on a Feature layer (new) output if your schema has changed, yet your feature layer output was configured to replace existing features and schema each time the analytic is started. This warning can be ignored if this was an intentional change.

This message is expected behavior. You can either edit the analytic to revert to the previous schema or configure a new feature layer output that replaces existing features and schema each time the analytic is started.

A published service with the name 'yourOutputName' already exists with the organization. Service names must be unique across the organization. Please use a different name.

When creating a new Feature Layer output, a unique name must be specified for the output layer. Feature layer (service) names must be unique across the organization since each feature layer exposes a REST endpoint service URL to access the layer.

You may encounter this message if you deleted a feature layer or removed a feature layer node and then configured the Feature Layer (new) output again. If the real-time or recurring big data analytic has run or is running since the feature layer was deleted, the feature layer would have been recreated by the running analytic. Therefore, when you try to configure this new feature layer output with the same name, the name is flagged because it already exists.

To resolve this, stop the real-time or recurring big data analytic. Navigate to the Layers page and delete the feature layer. Return to your analytic and recreate the Feature Layer (new) output with the desired name.

The Kafka broker or topic is inaccessible

In order to send output messages to Kafka, the destination Kafka broker and topic must be externally accessible on the Internet for Velocity to communicate with it.

The SMTP server is inaccessible

When configuring an Email output, you must provide the address of an SMTP server. Velocity sends the request to send an email to the SMTP server, however, the SMTP server will actually send the email.

In order to send an email request to an SMTP server, the SMTP server must be externally accessible on the Internet in order for Velocity to communicate with it.

The SMTP server is enforcing rate limiting

If sending many output features to the Email output, your SMTP server may rate limit your requests.

When configuring the Email output, you must provide an address to an SMTP server which is accessible to Velocity. Some SMTP servers and administrators may choose to rate limit how many emails can be sent per day by a single user.