Recurring Delivery getting Stuck without any error. | Community
Skip to main content
nadeema90078524
Level 2
April 7, 2017
Solved

Recurring Delivery getting Stuck without any error.

  • April 7, 2017
  • 4 replies
  • 2047 views

Hi ,

I have a premise installation. I  have a campaign workflow  scheduled since last year. All of sudden since past week it is getting stuck at delivery activity without any errors.We do not have any approvals. Delivery is going into finished state and delivery file is getting created properly. However in same workflow downstream i have update query to update broadlogrcp table  to update two fields. It is sticking at Delivery activity only and when manually i am running from the delivery task again it is completing successfully without any error. But on schedule basis it is not running till the end. Audit logs does not have any error information.

Please guide me how can i fix.

 

Thanks

Nadeem

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Amit_Kumar

Hi Nadeem,

 

did you have a same server and client build number? this happened with me once i have a mismatched build number otherwise do as Florent suggested.

Regards,

Amit

4 replies

florentlb
Level 10
April 7, 2017

Hi Nadeem,

I'll check with the team to see if this is a known issue. Can you provide more details on your installation (server and client build numbers) as well as sending a screenshot of your workflow?

In the meantime, can you raise a ticket to Adobe's support?

Thanks,

Florent.

florentlb
Level 10
May 2, 2017

Hi Nadeem,

Were you able to resolve your issue?

Florent.

Amit_Kumar
Amit_KumarAccepted solution
Level 10
May 4, 2017

Hi Nadeem,

 

did you have a same server and client build number? this happened with me once i have a mismatched build number otherwise do as Florent suggested.

Regards,

Amit

Amit_Kumar
Level 10
May 4, 2017

Hi Nadeem,

 

did you have a same server and client build number? this happened with me once i have a mismatched build number otherwise do as Florent suggested.

Regards,

Amit