A sticky session should end for an explicit reason, not only because a fixed timer expired. In an authorized data job, I would track elapsed time, request count, idle time, location checks, and consecutive failures.
The session can close after its logical item is validated. It may close earlier if the route becomes unhealthy or returns content for the wrong market. If the worker must retry the item, it should record why the old session ended and whether the new attempt still satisfies the same data contract.
An item ID should not depend on the session identifier. That lets the job move to a new route without creating a duplicate record. Credentials and cookies should stay out of the shared operational log.
What retirement rule has been easiest to operate: task completion, TTL, request count, idle interval, or a combination?
The session can close after its logical item is validated. It may close earlier if the route becomes unhealthy or returns content for the wrong market. If the worker must retry the item, it should record why the old session ended and whether the new attempt still satisfies the same data contract.
An item ID should not depend on the session identifier. That lets the job move to a new route without creating a duplicate record. Credentials and cookies should stay out of the shared operational log.
What retirement rule has been easiest to operate: task completion, TTL, request count, idle interval, or a combination?