GraphQL Interface reports "Unexpected end of JSON input"

• Related Articles

• Checklist: SAP Interface does not work

  Time estimate:  30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick ...

• GraphQL interface editor only works with internet access

  Description The GraphQL Interface Editor requires an active internet connection. If this is not available or the file has been removed from the CDN, the editor will not work. This has been changed. The GraphQL Interface Editor no longer requires an ...

• The Azure Process Gateway (AccessAzure) behaves unexpected when communicating to an EventHub via JSON.

  Summary The communication to an EventHub via JSON of the Azure Process Gateway (AccessAzure) behaves unexpected. DescriptionThe communication to an EventHub via JSON of the Azure Process Gateway (AccessAzure) behaves unexpected. Solution This issue ...

• Unexpected State detected for License dongles

  The license central indicates an unexpected state for a certain dongle if the state of the dongle - given in a license request or license confirmation file - does not match that one which is calculated by the license central. A reason for this can be ...

• GraphQL - Wildcard * sometimes not working for Recources Label and Identification

  Description Filters in GraphQL interface sometimes do not provide desired results. If filtering on an empty string, only those objects are displayed that have an empty string at the filtered items. However, the filter should be disabled and show all ...