Freshdesk migration which doesn't support time entries runs in unwanted behaviour

[dominikklein]

Infos:

• Used Zammad version: stable 5.1 as of 4pm UTC, 8th April
• Installation method (source, package, ..): any
• Operating system: any
• Database + version: any
• Elasticsearch version: any
• Browser + version: any

Expected behavior:

• Freshdesk migration should not spam the log and it should also not run in the retry mechanism which leads to a long-running migration.

Actual behavior:

• The log will be spammed with response errors and the migration runs in the retry mechanism when the Freshdesk system does not support time entries (e.g. low plan).

Steps to reproduce the behavior:

• Try to migrate a Freshdesk system that has no time entry support (low plan)
• Check the log and the long-running migration for every ticket.

Yes I'm sure this is a bug and no feature request or a general question.