was previously read from the environment

... only if ENABLE_TESTING_ROUTES is defined in the environment

more for maintaining coverage than actually necessary ;)

update_status uses result backend, which seems very hard to mock

because this is the logger that shows task result

this is necessary, otherwise the synchronise tasks called with
.apply() fail silently

iterating over keys & then non-atomically fetching value ...