Pending Delivery | Community
Skip to main content
S
Sanjana12
Level 6
August 11, 2024
Question

Pending Delivery

  • August 11, 2024
  • 2 replies
  • 908 views

Hi, there was a situation in which a bulk delivery was stuck as "Target Ready" for almost an hour until somebody using an anonymous admin account applied "Wake Up" on the Campaign workflow and the delivery resumed again.Is it possible that applying wake up helped to resume the delivery or was it because of some other issue?

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

2 replies

Amine_Abedour
Community Advisor
Amine_AbedourCommunity Advisor
Community Advisor
August 13, 2024

Hello @sanjana12,

 

it seems like the operationMgt workflow was Ko during this hour. It is responsible for orchestrating the campaigns.

Please check logs of operationMgt workflow to try to understand what was the problem.

 

Br,

Amine ABEDOUR
S
Sanjana12Author
Level 6
August 13, 2024

Hi, can you provide some hints because the workflow ran without any errors on that day and at that time.

MeitMedia
MeitMedia
Level 4
August 27, 2024

Hi @sanjana12 

 

The best reason causing such issues in campaign deliveries is operationMgt workflow usually as mentioned by @amine_abedour,  but if you say that the operationMgt workflow ran without errors, and the bulk delivery was stuck in the "Target Ready" state, there are a few potential factors that might have contributed to the situation:

  • Workflow Latency: The operationMgt workflow, although it ran successfully, might have experienced latency or a temporary hang that wasn't logged as an error. This could cause delays in processing and leave the delivery in a "Target Ready" state.
  • Database Locks or Delays: If the database was under heavy load or certain records were locked during that time, it could delay the transition of the delivery from "Target Ready" to the next step. The Wake Up action may have triggered a retry or forced the workflow to proceed.
  • Resource Constraints: If there were resource constraints (CPU, memory, etc.) on the server at that time, it could have impacted the workflow's ability to process the delivery promptly. The Wake Up command might have reprioritized the workflow's operations.
  • Temporary System Glitch: Sometimes, temporary glitches or deadlocks within the system can cause workflows to pause. Applying Wake Up forces the workflow to re-evaluate its state, which might have pushed the delivery past the stalled point.
  • Timing Issues: There could be a timing issue where the Wake Up action coincidentally aligned with the resolution of the underlying problem, making it appear as though the Wake Up was responsible.

Best regards,

MEIT MEDIA (https://www.meitmedia.com)

Find us on LinkedIn

Contact Us: infomeitmedia@gmail.com

 

 

    Terms & ConditionsAccessibility statement

    Loading footer...