Users can find additional help by visiting If the error is not directly related to the connector, then there is no actionįor the connector developer to take. If a user attempts to use a time series chart with a data source with no Looker Studio errors are errors unrelated to your connector code. For more information onĭebugging your connector, see Debug your code. Thorough testing can prevent these errors.Ĭonnector external errors can typically be fixed by reviewing error details (ifĪvailable) and debugging the code to identify the issue. Although theĬonnector completed execution, it did not satisfy the request from Looker GetData() request for three fields only returns data for two. Connector external errorĬonnector external errors occur after connector execution. These errors should be anticipated and handled with user-friendly explanationsįor more information on handling connector internal errors, seeīest practices for handling connector errors. For example, if aĬonnector cannot parse an API response during the execution of getData(). Connector internal errorĬonnector internal errors occur during connector execution. These errors occur due to developer-authored code. The types and causes of errors that a user may encounter when using yourĬonnector typically fall into one of the following three categories:Ĭonnector internal and external errors should be handled by the connectorĭeveloper. Info: To learn more about handling exceptions in JavaScript see Messages work, and how to properly handle connector errors. This document describes errors that can happen with connectors, how error Present users with actionable error messages that outline corrective steps for To provide a good user experience your code should handle errors correctly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |