Core Workflow - EBS (MOSC)

MOSC Banner

How To Get WF Timeouts To Move Forward?

in Core Workflow - EBS (MOSC) 7 commentsAnswered ✓

We are playing around with creating some training workflows and have placed a notification that should timeout after 15 minutes in a test workflow. The first notification goes out successfully but then gets stuck. We eventually get the #STUCK error message after the background engine for stuck processes runs. Here is the basic process:

1) Script runs to find an email addr for a person

2) If NULL, then a notification goes to email admin

3) After 10 minutes, a loop counter is incremented, then we start at #1 again

4) After 3 attempts (loops) it escalates to their manager.

This gets stuck in step #3 and only one notification is successfully sent. Any thoughts as to why this is occurring? It's probably one small setting.... right? I hope!

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS Workflow Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center