orchestrator api - adding queue items is not working
hello folks,

i am trying to invoke the orchestrator api to send a simple queue message to them.

and when i perform it, i am getting the http status code (200) and apparently it is okay. but that event message is not arriving.

i am using postman to authenticate ([https://orchestrator/api/account/au…](https://orchestrator/api/account/authenticate)
hello, thank you so much for you assistance i have tried in soapui and it was working properly.

in the postman, i was able to get the items added into the queue after adding all the default settings of it.

[image]

now it is working fine.

regards,
i suspect that the resource\_exhausted message may have originated from a back-pressuring committer node ([code](https://github.com/digital-asset/daml/blob/926fb5997a795e7f80443a9a3ba7898b1568d158/ledger/participant-integration-api/src/main/scala/platform/apiserver/services/apisubmissionservice.scala#l155-l157)). if that’s the case, i believe the approach should be the same: change the configuration if you need and make sure to handle those errors with the appropriate retry strategy. hey! your token request has been successfully added to the [accointing.com](http://accointing.com) database. it should be available today at 11:00 p.m. gmt. (7 a.m. et) well, i raised an issue with id support whom escalated it with engineering or something and it's now working. they did say they'd text me updates and haven't received anything from them so whether they did anything or whether it just started working.. who knows. 

but yeah, looks like the answer is calling / talking to support. hi daniel,

that error message indicates either a dodgey account code, incorrect queue for job size/time limits or exceeding number of jobs allowed.

you need to specify a valid account code. n02 is not a valid budget.

regards,

ros. Hi Lena,

Message Center deliveries are Continuous deliveries. As soon as you get a new event related to that delivery, the email delivery status will get set to InProgress followed by Finished or Retry Pending.

Before deciding on deletion, we should help identify why it is failing. Definitely there is something wrong on yoru template.

If you fix that, this problem will go away.

Can you please point out the error that causes the delivery to fail?

If you still wish to get rid of problematic delivery, right click on its record in List View and hit Stop.

Regards,

Vipul




[View solution in original post](/t5/adobe-campaign-standard/is-it-ok-to-delete-erroneous-deliveries/m-p/303524#M5132) send me a message and i'll see what we can do for you.
 


  
 


 be sure to include a description of the issue, your username, and the error message you are prompted with when you attempt to create a ticket.
 


  
 


 received your message. topic locked. welcome rm.  the smtp server listed in the post is the correct one.  the is a short time lag between account creation and full activation on the server. please retry the outlook set up again and let us know if it successful. 
 
thank you hi there, guys!

[@mitrpathak](/u/mitrpathak) i think i get your point.

it’s about naming requests. the way that postman determines how the requests inside the generated collection will be named after importing.

if i get that right, when you are importing a new api into postman, you will find a collapsed panel “sh… A trigger is not what you want.


What you need is a scheduled job.


Take a look at the official documentation on the subject:


[Scheduling Jobs with Oracle Scheduler](http://docs.oracle.com/cd/B28359_01/server.111/b28310/scheduse.htm#i1033533)


Feel free to ask more questions if you find any trouble when creating your scheduled job. first of all, you need to check if you are using a self-signed certificate.

if so, you have to accept it first: double-clicked on the request in the network pane, and ow prompted you whether you wanted to accept the certificate.

other option will be to use the [overwolf.web.sendhttprequest()](http://developers.overwolf.com/documentation/sdk/overwolf/web/#sendhttprequest) funct…