Subversion Repositories SmartDukaan

    /**

     * Itel activation from Carlcare, Transsion's own after-sales endpoint. 50 imeis every 5

     * minutes, which spreads the work over the whole day rather than bursting: 14,400 lookups a

     * day against a pending pool of ~10,400.

     *

     * The 5-minute cadence is safe here in a way it was not for vivo, whose comment below records

     * why that pattern ran away: there, a failed lookup wrote no row, so createTimestamp was not

     * bumped and the same imei was eligible again five minutes later. This service stamps the row

     * on EVERY outcome, failures included, so each tick advances past the imeis it asked about

     * and a failure costs one retry tomorrow rather than one every five minutes.

     *

     * It is one plain signed GET per imei -- no captcha solver, no ChromeDriver -- so it does not

     * contend with the oppo/realme pass. Both this and the 23:00 DCR pull write Itel rows and

     * need no coordination: the pool query returns only imeis whose activationTimestamp is still

     * null, so whatever one has filled has already left the other's pool.

     */

    @Scheduled(fixedDelay = 5 * 60 * 1000)

    public void carlcareImeiActivation() throws Throwable {

        scheduledTasks.checkCarlcareImeiActivation();

    }