[FEAT] Retry on timeout failed

[yusef-ho]

Is this a new feature request?

• I have searched the existing issues

Wanted change

Error Handling

Reason for change

Thanks for the nice tool first.
I've been use it for couple of weeks. It was working well.
But in these two days, there are two conditions occurred,

1. timeout of anti-captcha
2. connection aborted

currently, once i received the email of the failed job, i entered the container to execute the command in crontab manually.
Probably add the feature of retry?

Proposed code change

No response

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[TommyE123]

Apologies for the delayed reply.
I have encountered similar issues myself, so it would be good to find a solution here!

Currently, the cronjob directly calls the packt-cli command. To better handle potential timeouts, I think we'll need to extract the command into its own script. This script can then wrap the packt-cli call and check if it timed out, possibly by inspecting the last line of the log file.

Additionally, we'll need to determine suitable retry logic in the script - how many retry attempts and over what duration before declaring failure.

Another consideration is whether the packt-cli Python script itself should really handle retries internally. This would keep the cron side simple but would need an external change outside of this container.

I'll try and spend some time reviewing in more depth. Please let me know if you have any other thoughts on the best way to structure this to make the cronjob more robust to timeouts.

Also, if you have any code changes to suggest, I'm open to reviewing pull requests that could improve the cronjob's reliability.

Thanks for logging this issue and I'm confident we can find an optimal approach 🙂