Skip to content

What's New

Platform 2018.10.18

Platform · 2018.10.18 · 18 October 2018

ImprovementOn production sites

On production sites

This release gives you control over long-running background jobs in async_callback_actions. Some long tasks were too slow to finish, and you had no information about limits, errors or timeouts.

Choose a priority for each job

Set priority to high, default or low. If you do not set it, the priority is default. Each priority has a time limit: high allows 1 minute, default allows 5 minutes and low allows 4 hours. Write your code so it runs fast enough for its priority.

Retry a failed job

Set max_attempts to try a job again if it fails, for example after a timeout, an error in your code or a third-party API that does not answer. The default is 1. Use it with care, because every attempt uses resources.

See what went wrong

When a job fails or times out, it is logged. You can read the log with insites-cli logs.

Example:

async_callback_actions: delay: 10, priority: low, max_attempts: 2