# Bypass Store and Forward Transaction Group option

**URL:** <https://forum.inductiveautomation.com/t/bypass-store-and-forward-transaction-group-option/8023>\
**Category:** Ignition\
**Created:** [February 19, 2014, 9:57am UTC](https://forum.inductiveautomation.com/t/bypass-store-and-forward-transaction-group-option/8023 "2014-02-19T09:57:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![george](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/george/32/14066_2.png) [@george](https://forum.inductiveautomation.com/u/george)\
**Post date:** [February 19, 2014, 9:57am UTC](https://forum.inductiveautomation.com/t/bypass-store-and-forward-transaction-group-option/8023/1 "2014-02-19T09:57:20Z")

</div>

I notice if I add a new Stored Procedure transaction group then by default the “Bypass Store And Forward” option is ticked.

Is there a reason for this? Can the Store and Forward mechanism cope with Stored Procedures if I were to untick the box?

(in my specific case the SPs are only taking input parameters and are not returning any values)

---

<div class="post-metadata">

**Author:** ![greg.simpson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/greg.simpson/32/3135_2.png) [@greg.simpson](https://forum.inductiveautomation.com/u/greg.simpson)\
**Post date:** [July 9, 2014, 6:30pm UTC](https://forum.inductiveautomation.com/t/bypass-store-and-forward-transaction-group-option/8023/2 "2014-07-09T18:30:26Z")

</div>

Looking at the code for this and it appears that you can use the store and forward as long as there are no output or return parameter mappings.