REFramework State Machine — The Four States
Understanding the purpose and transitions of each REFramework state is critical for correct implementation.
- Initialization (Init) — loading config, opening applications, verifying readiness; transitions to Get Transaction Data on success or End Process on failure
- Get Transaction Data — fetching next queue item from Orchestrator or defining custom transaction sources; transitions to Process Transaction (item available) or End Process (no more items)
- Process Transaction — executing the actual business logic for the current transaction item; transitions to Get Transaction Data on success, or handles exceptions
- End Process — cleanup logic, closing applications, final logging; always the terminal state
- State transitions — understanding when to retry vs end, how retries decrement retry counter
- Config.xlsx — system settings, app settings, constants, credentials references in REFramework
Queue-Based REFramework Design
The standard REFramework uses Orchestrator queues as the transaction data source.
- TransactionItem variable — type QueueItem, carries Reference, SpecificContent, DueDate, Priority
- Get Transaction Item activity — fetching from Orchestrator queue with max retry count awareness
- Setting transaction status — SetTransactionStatus to Successful, BusinessException, or ApplicationException
- Retry logic — Orchestrator retries up to MaxRetryNumber on ApplicationException; no retry on BusinessException
- Queue item SpecificContent — accessing custom fields added during Dispatcher phase
- Bulk queue upload — Dispatcher design pattern for populating queues before Performer runs
Exception Handling in REFramework
REFramework has a specific exception handling pattern that separates business logic failures from system failures.
- BusinessRuleException — expected failures (e.g. invalid data, missing record) — marks item as BusinessException, no retry
- System.Exception (ApplicationException path) — unexpected failures (e.g. UI crash, network error) — triggers retry up to MaxRetryNumber
- shouldMarkJobAsFailed flag — controls whether a System.Exception terminates the entire job after max retries
- Recovery logic — re-Init after system exception (re-open app, clear state) before retry
- Screenshot on failure — capturing UI state at exception point in Process Transaction
- Logging strategy — consistent log messages at each state transition for production diagnostics
Config File and Asset Management
The REFramework Config.xlsx and Orchestrator assets work together to make bots configurable without code changes.
- Config dictionary — loaded in Init, accessible throughout REFramework via Config("key") references
- System settings tab — runtime parameters: max retries, log levels, application wait times
- Assets tab — Orchestrator asset names for credentials, URLs, environment-specific settings
- Constants tab — business rules and thresholds that are stable across environments
- Environment separation — Dev/Test/Prod asset differences managed through Config without code changes
- Extending Config — adding custom keys, handling missing keys gracefully in Init
Production REFramework Support
Production REFramework bots require specific monitoring and recovery patterns.
- Job failure analysis — identifying which state failed, reviewing Orchestrator logs, exception messages
- Infinite loop prevention — detecting and breaking unexpected state loops in production
- Performance tuning — reducing transaction processing time, optimizing Get Transaction Data calls
- Hypercare support — monitoring newly deployed REFramework bots through initial production weeks
- Regression after UiPath updates — verifying REFramework template compatibility with new Studio versions
Frequently Asked Questions
What REFramework job support do you provide?
We provide real-time REFramework support — state machine design, Init/Get Transaction/Process Transaction/End Process logic, queue integration, business vs system exception handling, config file management, retry design, production failure analysis, and hypercare support. REFramework is one of the most common UiPath interview topics and we also provide proxy interview support for REFramework scenario questions.
How do you handle business vs system exceptions in REFramework?
BusinessRuleException marks the queue item as BusinessException (no Orchestrator retry, counts as failure but not system crash). System.Exception (ApplicationException path) triggers Orchestrator retry up to MaxRetryNumber, with a re-Init recovery step to restore application state before each retry. We help design this correctly for your specific process requirements.
Can you help with REFramework production failures?
Yes. Production REFramework support includes log analysis, failed transaction diagnosis, state transition debugging, queue backlog analysis, retry exhaustion scenarios, and hypercare monitoring. We help identify root causes and implement fixes in real time.
How do I explain REFramework in a UiPath interview?
We provide proxy interview support for REFramework questions — state machine architecture walkthrough, dispatcher/performer design, exception handling strategy, config file design, and queue retry logic. Contact us before your interview for real-time live guidance.
Ready to get real-time expert support?
Same-day start. Confidential. All major time zones covered.