500-445 · Question #50
How long before incoming activities coming to aliases, for which there are no workflows configured, are moved to the exception queue?
The correct answer is A. 60 minutes. Option A (60 minutes) is correct because most workflow platforms use a 60-minute threshold as the default timeout for activities arriving at aliases that lack configured workflows - after this window, the system automatically routes them to the exception queue to prevent items…
Question
How long before incoming activities coming to aliases, for which there are no workflows configured, are moved to the exception queue?
Options
- A60 minutes
- B120 minutes
- C240 minutes
- D24 hours
How the community answered
(55 responses)- A93% (51)
- B2% (1)
- D5% (3)
Explanation
Option A (60 minutes) is correct because most workflow platforms use a 60-minute threshold as the default timeout for activities arriving at aliases that lack configured workflows - after this window, the system automatically routes them to the exception queue to prevent items from being silently lost or stuck indefinitely.
Options B (120 minutes), C (240 minutes), and D (24 hours) are distractors representing longer wait times that would leave unhandled work sitting idle too long, defeating the purpose of exception handling. These values may seem plausible because they follow a pattern of doubling or scaling up, but the platform default is the shorter 60-minute window.
Memory tip: Think "60 = one hour to catch exceptions" - a single hour is the standard grace period before the system escalates unrouted work. Associate it with the common "1-hour SLA check" mindset in operations: if nothing has picked it up in an hour, it needs attention.
Topics
Community Discussion
No community discussion yet for this question.