Orchestration forever failing with `DurableTask.Core.Exceptions.TypeMissingException: Orchestration not found`

Scenario:
1. A client starts an orchestration
2. Orchestration is queued up, and picked up by a worker
3. Worker has no knowledge of that orchestration and fails with `DurableTask.Core.Exceptions.TypeMissingException: Orchestration not found`
4. That orchestration will be retried multiple times using an exponential backoff strategy, until it retries every 10 minutes
5. Eventually, we get to a point where the message is considered poison: `Message [ExecutionStarted] with ID b257da02-0535-4d61-86ce-d23430564c2a has been dequeued 80 times and is now considered poison`
5. However, that message seems to be stuck forever, or until a new worker is deployed that knows this orchestration and handles it.

Is there some sort of configuration to ensure that we don't retry forever, and rather the message is dead lettered, or the orchestration cancelled and failed?

Note: _The above scenario can happen in the case of a deployment rollback, where we had some orchestration started, but then the application (client and worker) was rolled back to an earlier version where that orchestration did not yet exist in the code base._