Performance considerations when working with the Execution Pipeline Application Programming Interface (API)
- Last UpdatedApr 08, 2026
- 1 minute read
- Execution Pipeline steps should complete quickly. Steps should have short and predictable execution times.
- Execution Pipeline steps should be written to minimize locking of the RealTime database (RTDB). New locks should only be taken within their required scope and should be released when they are no longer needed.
- Execution Pipeline steps should not make use of Thread.Sleep() or similar methods that suspend thread execution.
- Any exceptions that might be raised by the step should be caught and handled gracefully within the step.