Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

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

Avatar

Avatar
Give Back
Level 2
anumola79005307
Level 2

Likes

5 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Ignite 1
Validate 1
Boost 5
Boost 3
View profile

Avatar
Give Back
Level 2
anumola79005307
Level 2

Likes

5 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Ignite 1
Validate 1
Boost 5
Boost 3
View profile
anumola79005307
Level 2

22-09-2019

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 50
Employee
Adhiyan
Employee

Likes

239 likes

Total Posts

342 posts

Correct Reply

124 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 100
View profile

Avatar
Boost 50
Employee
Adhiyan
Employee

Likes

239 likes

Total Posts

342 posts

Correct Reply

124 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 100
View profile
Adhiyan
Employee

26-09-2019

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

Answers (2)

Answers (2)

Avatar

Avatar
Validate 1
MVP
Anita_p
MVP

Likes

116 likes

Total Posts

118 posts

Correct Reply

28 solutions
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Validate 1
MVP
Anita_p
MVP

Likes

116 likes

Total Posts

118 posts

Correct Reply

28 solutions
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Anita_p
MVP

24-09-2019

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

Avatar
Give Back
Level 2
anumola79005307
Level 2

Likes

5 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Ignite 1
Validate 1
Boost 5
Boost 3
View profile

Avatar
Give Back
Level 2
anumola79005307
Level 2

Likes

5 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Ignite 1
Validate 1
Boost 5
Boost 3
View profile
anumola79005307
Level 2

26-09-2019

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