Skip to main content
Question

Application message address label for call back function fails but does not get re-executed.

  • January 28, 2025
  • 1 reply
  • 20 views
N
Do Gooder (Partner)
Forum|alt.badge.img+2
  • nija.nt
  • Do Gooder (Partner)
  • 4 replies

Dear All,

I am currently working on a REST integration for a customer in APPS10 that utilizes callback functions.

Occasionally, the address label for the callback function fails to execute automatically. However, when the address label is manually re-executed, it completes successfully. 

I am wondering why the failed label does not execute automatically. The REST Sender has been configured with the parameters MAX_RETRIES and RETRY_INTERVAL. Could these settings be having no effect on the failed label for callback function?

Additionally, is there any workaround that would allow for the automatic execution of these failed messages without requiring manual intervention?

Thank you in advance for your assistance.

Kind regards,

Nija 

1 reply

T
Do Gooder (Customer)
Forum|alt.badge.img+3
  • truth_trump
  • Do Gooder (Customer)
  • 22 replies
  • January 29, 2025

Hi ​@nija.nt 
The issue with the callback function not re-executing automatically could be due to:

  1. REST Sender Configuration – Ensure MAX_RETRIES and RETRY_INTERVAL are correctly set and applied. Check logs for retry attempts.
  2. Message Handling Issues – Confirm that failed messages are marked as "Retry Pending" instead of "Error" to allow automatic re-execution.
  3. System Logs & Error Messages – Review logs for errors or exceptions preventing retry execution. Enable debugging if needed.
  4. Processing Logic for Retries – Verify if a job or process is responsible for retrying failed messages and ensure it’s configured correctly.
  5. Workaround – Consider a custom job or script to detect and re-execute failed callback messages automatically.

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings