Expand my Community achievements bar.

Announcing the launch of new sub-community for Campaign Web UI to cater specifically to the needs of Campaign Web UI users!
SOLVED

The delivery cannot be started because the resources are not available. Please restart the analysis process.

Avatar

Level 2

Hi ,

We are facing an issue with an error in Delivery

The delivery cannot be started because the resources are not available. Please restart the analysis process.

What we are doing is

1. Executing the campaign

2. Marked the delivery for confirming  before sending

3. Next day morning checking the delivery and we see "The delivery cannot be started because the resources are not available. Please restart the analysis process "

We have on premise data and delivery via MidSourcing . Can anyone give some pointers here ?

Thanks and Regards,

Anumol Antony

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi Anumol,

When you are waiting overnight with the delivery in the pending confirmation state , the database cleanup workflow which executes at 4AM by default may be is wiping off the temp tables associated with the delivery.

The cleanup script details are given in the doc here : Database cleanup workflow

If the deliveries are using mid-sourcing and the state is start pending , then it deletes the linked information.

This is very likely what's happening in your case.

Can you please do the two tests to confirm this theory

1>. Use a test delivery and change the routing account from mid-sourcing to internal email delivery . Let the DB cleanup run and see in the morning the status of the delivery.

You should not have the error.

Do the same test next day but with the delivery routing set to mid-sourcing.

It should throw the error.

2>. use your standard workflow and setup the delivery in the usual way but stop the database cleanup workflow from executing next morning.

It should not throw error.

Enable the database cleanup for the next day with the same setup

it should throw the error

Regards,
Adhiyan

View solution in original post

3 Replies

Avatar

Level 7

Hi Anumol,

Can you do some checks:

  1. if the delivery was created using a custom Delivery Template and that Delivery Template is still in place/not deleted?
  2. "To" in the delivery has been configured correctly- Main->Resulting from the upstream

Thanks,

Anita

Avatar

Correct answer by
Employee

Hi Anumol,

When you are waiting overnight with the delivery in the pending confirmation state , the database cleanup workflow which executes at 4AM by default may be is wiping off the temp tables associated with the delivery.

The cleanup script details are given in the doc here : Database cleanup workflow

If the deliveries are using mid-sourcing and the state is start pending , then it deletes the linked information.

This is very likely what's happening in your case.

Can you please do the two tests to confirm this theory

1>. Use a test delivery and change the routing account from mid-sourcing to internal email delivery . Let the DB cleanup run and see in the morning the status of the delivery.

You should not have the error.

Do the same test next day but with the delivery routing set to mid-sourcing.

It should throw the error.

2>. use your standard workflow and setup the delivery in the usual way but stop the database cleanup workflow from executing next morning.

It should not throw error.

Enable the database cleanup for the next day with the same setup

it should throw the error

Regards,
Adhiyan

Avatar

Level 2

Hi Adhiyan,

Thank you for the reply. What  I have found is that , the issue is due to validity period set in Delivery . The Delivery Duration is set as 4h, which means after 4 hours system will not be able to send the delivery  as the validity is expired.

The moment the validity expires  system is promoting us to do start the analysis again. The clean up workflow is not really deleting  and broad log or delivery here.

Thanks and Regards,

Anumol Antony