Setting up

    Troubleshooting

    When you test the connection

    MessageWhat to do
    Add the Event Hub connection string on the Connect formPaste the connection string on the Connect form and choose Save.
    The connection string has no EndpointCopy the whole connection string from Syndigo again. It starts with "Endpoint=sb://".
    The Endpoint must be an Azure Event Hubs namespaceThe address in the connection string isn't an Event Hub. Ask Syndigo for the right one.
    No event hub: add EntityPath to the connection string or fill in Event hub nameFill in Event hub name on the Connect form.
    The connection string needs SharedAccessKeyName and SharedAccessKeyThe key is missing. Copy the whole connection string again.
    The Event Hub refused the keyThe key is wrong or has been changed. Ask Syndigo for a new connection string.
    There's no event hub with that nameCheck Event hub name, or the hub name in the connection string.
    Couldn't reach the Event HubTry again in a few minutes. If it keeps happening, check the address with Syndigo.

    When a product isn't sent

    When a product is skipped, the reason is one of these.

    ReasonWhat it means
    Deletions aren't sent to SyndigoDeleted products are never sent. Remove them in Syndigo yourself if needed.
    No record idThe product has no id to send. If you set Record id attribute, check that field has a value on the product.
    No mapped attributes have a valueNone of the fields you mapped have a value on this product, or none of them are in your Syndigo attributes list. Check the mapping.

    If a record reaches Syndigo with missing attributes, check that each attribute is both in your Syndigo attributes list and mapped on the flow. Attributes that aren't in the list aren't sent.