Indicates the provider skips records or pages that cannot be parsed due to malformed JSON, and continues processing the remaining data.

Data Type

bool

Default Value

false

Remarks

When set to true, if the add-in encounters a JSON parsing error while processing an API response, such as a structurally invalid JSON, it will log the error and skip the affected record or page rather than throwing an exception. This allows a partial result set to be returned even when some data is unprocessable.

• true: Parsing errors are logged and the add-in continues to process the consequent page if applicable.
• false (default): Any parsing error causes the add-in to throw an exception and halt query execution.

Pagination Behavior: The effectiveness of this property when skipping a page depends on the Jira deployment type:

• Jira Data Center: Uses limit/offset-based pagination. If a page response is malformed and skipped, the add-in can still calculate the offset for the next page and continue paginating normally.
• Jira Cloud: Uses cursor-based pagination with a nextPageToken returned in each response. If the response is truncated or invalid, the nextPageToken will be absent. In this case, pagination cannot continue and the add-in will stop after the affected page, returning only the data retrieved up to that point. Records on subsequent pages will not be returned.

NOTE: This property does not fix the underlying data issue. It is intended as a workaround to allow partial data retrieval while the root cause, typically a custom field with a malformed structure or a truncated large response, is addressed at the Jira level. Consider using the ExcludeCustomColumns property to avoid requesting the problematic fields altogether.