Future method completes first before the queueable

Question

My scenario is: A future method is on a queueable class. Queueable job comes first before the Future job in the Apex Jobs. Upon checking the completion date(time), the future method is completing first before the queueable.

The queueable is getting the ids that needs to be processed and creating/updating a custom object record while the future is using the ID for updating the custom object record by HTTPResponse.

The queueable that has 12:48AM completion date(time) is updating the custom object record that the future method has already update (12:47). My question is, is there a chance to delay the running of future method since they are both async? Thank you.

Answer 1

There is no surity that one async apex will run before another async when they are invoked separately (or rather paralelly).

Instead what you can do is, invoke the future from queueable execute method like below:

public class poc {

    public class myqueue1 implements Queueable {
        public void execute(QueueableContext context) {
            // some logic  
            myFuture();
        }
    }

    @future
    public static void myFuture(){
        // logic
    }
}

OR, convert the future into queueable and invoke it at the end of 1st queueable execute method. Example:

public class poc {

    public class myqueue1 implements Queueable {
        public void execute(QueueableContext context) {
            // some logic  
            System.enqueueJob(new myqueue2());

        }
    }

    public class myqueue2 implements Queueable {
        public void execute(QueueableContext context) {
            //some logic      
        }
    }
}

Answer 2

@future methods & Queueable are enqueued in a message queue that doesn't guarantee execution order. Convert the future method into Queueable class and enqueue.

Answer 3

Asynchronous method do not guarantee running time, it just like whichever get the resource first will get executed first despite of the fact which is called first.

So, instead of doing dependent things in future and queueable methods, you should go with the queueable chaining. first get the record IDs which currently and enqueue another job which will utuilize those IDs to do rest of the processing.