Azure Service Bus Schedule a message broken?

Thank you Charlie and BKBK for your advice. I did some dumping and determined that yes, despite the documentation having the example of 

scheduleResponse = sb.scheduleMessageToQueue(myQueue, schedMessage)

where myQueue is an object, the method does actually expect the string queue name.

Changing the code to 

scheduleResponse = sb.scheduleMessageToQueue("Q_006", schedMessage)

gets me past the error of "scheduleMessageToQueue method was not found". 

Now I get "Unknown Field : ScheduledEnqueueTimeUtc".

I thought maybe the format of the time was the issue, even though the doc example had  "02/02/2020", so I dug into the Azure documentation and found it was expecting a DateTimeOffset: an ISO8601 datetime. 

So, changing the parameter to be the string queue name, and formatting the send time as ISO8601: 

    schedMessage5 = {
        "messageId" = "005",
        "messageBody" = "message body",
        "ScheduledEnqueueTimeUtc" = dateTimeFormat(dateAdd("n", 10, now()), "iso")
    }
    try {
        scheduleResponse = sb.scheduleMessageToQueue("Q_006", schedMessage5);
    } catch (any e) {
        writeDump(e);
    }

I get this error instead

struct

And since dumping the queue object showed a similar method 

scheduleMessage(java.util.Map)

I tried calling that method with an ISO8601 also 

scheduleResponse = myQueue.scheduleMessage(schedMessage5);

  But got the same error message about "Unknown Field : ScheduledEnqueueTimeUtc"

Luckily I don't actually need the scheduled message functionality, but maybe my exploration of it will be helpful to someone else.

@lisar36119501 , I suspect that the cause of the error is myQueue. In your code, it is passed as a string argument. I can understand why. That is what ColdFusion's Azure Service Bus documentation suggests.

However, it is unlikely for myQueue to be a string. My reasoning follows.

ColdFusion's Azure Service Bus documentation contains examples such as

tempQ = sb.createQueue("Queue18") 
//writedump(tempQ) 
mypath=tempQ.getPath() 

which suggest that createQueue() returns a complex object. In addition, the documentation says that the syntax for scheduleMessageToQueue is:

scheduleMessageToQueue(String queuePath, Map metadata)

In your code, schedMessage is a struct, hence of type CaseInsensitiveMap. That's fine. But myQueue is probably not a string. As I have shown, myQueue is a complex object which has the queue-path as one of its attributes. Hence the following suggestions.

1.  The documentation says that a queue's path is given by myQueue.getPath(). So use myQueue.getPath() in place of myQueue.
   

   myQueue = sb.createQueue("q_006");
       schedMessage = {
           "messageId" = "001",
           "messageBody" = "message body",
           "ScheduledEnqueueTimeUtc" = dateAdd("n", 10, now())
       };
       try {
           scheduleResponse = sb.scheduleMessageToQueue(myQueue.getPath(), schedMessage);
       } catch (any e) {
           writeLog(file = "azureErrors", text = e, type="Error");
       }

2.  If the above suggestion doesn't work, find an alternative way to get the queue-path.

/** 
Look for ways to obtain the queue-path from 
the information in the metadata or the queue object.  
**/
myQueue = sb.createQueue("q_006");
writedump(var="#getMetadata(myQueue)#", label="GetMetadata(myQueue)");
writedump(var="#myQueue#", label="myQueue");

/* What do the dumps tell you? Here I have assumed the dumps say the path is myQueue.name */
myQueuePath = myQueue.name;

    schedMessage = {
        "messageId" = "001",
        "messageBody" = "message body",
        "ScheduledEnqueueTimeUtc" = dateAdd("n", 10, now())
    }
    try {
        // this errors with "The scheduleMessageToQueue method was not found."
        scheduleResponse = sb.scheduleMessageToQueue(myQueuePath, schedMessage)

    } catch (any e) {
        writeLog(file = "azureErrors", text = e, type="Error");
    }

Lisa, while I've never used the ASB feature, and I'm reading this on my phone, I might still be able to offer a useful suggestion. And although your code looks like it SHOULD work compared to the docs, here are two things to consider.

First, are you running this that you feel you must rely on writelog, because you can't produce output to the screen? Can you arrange to call it in such a way that you can? If so, it will simply make diagnosing things easier. 

For example, what do you see if you writedump(sb)?  That will list all the methods of that cfc instance, including their arguments. Indeed, then dump also your myqueue and schedmessage vars. Despite what our eyes tell us from your code, those may hold something that's somehow unexpected. 

Finally, there may also be more useful detail in the error than what your writelog is reflecting. How about dumping the e var within the catch?

Or (sometimes better still) remove the try/catch and just let the normal cf error dump to screen. Another benefit of that is you may see more detail in cf's exception.log (which may not be written to when you catch an error).

Of course, you can also tell writedump/cfdump to write its output to a file instead of the screen, if you must for some reason. 

Let us know what you find, or better if you may be able to use that info to resolve the problem on your own. Or maybe someone else will see a different solution for you.