Skip to Content

Work Manager 6.1: Transmit steps were not called during the transmit

Hi Experts,

We have an issue with the transmit action did not run during the transmit if there was a agentry code change earlier:

Steps to reproduce:

- Add a transmit step to the transmit action which includes some fetches such as Fetch WOs, Fetch Notifications, Fetch MainMenu. The transmit action was triggered by transmit button click.

-Uncheck MainFetch checkbox on the fetches, for example. The purpose of this was we wanted to make sure that the fetch in transmit step would be called rather than the main fetch.

-Publish all changes to server then clicked transmit to load the change.


The change was loaded to device but the transmit action (included the fetches) was not called so there was no Work orders and notifications were loaded. Just only the mainfetch ran. However, if we clicked the transmit button again, the transmit action was triggered and all work orders and notifications were loaded as normal.

Any recommendation is highly appreciated. Thank you so much.

1.png (25.6 kB)
2.png (22.5 kB)
2.png (22.5 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Aug 21, 2017 at 01:35 PM

    This sounds like it is working exactly as expected. When you published your change to the server and transmitted to download the change the client used the current definitions it had to connect and download and updates. Changes in the transmit action being run to download the new definitions will not take effect until the next time you transmit. The current running action definitions won't be replaced mid-action. The client has not way transition to the new transmit action that was just downloaded while it is still executing. As you mentioned, the next time you transmitted the new transmit action correctly executed as expected.


    Add comment
    10|10000 characters needed characters exceeded

    • Thanks Bill, yes the next time I transmitted it worked fine. However, if I continue to make any other change, even a simple change like text, transmitted again, only the main fetches were triggered. The transmit steps (with some fetches) I created earlier did not run until the next transmit. Did you think that's an expected behavior? I read somewhere that if we unchecked the main fetch attribute on any fetch, we were able to create an alternative fetch in transmit step and run it from there rather than from the main fetch. That did not happen in my case. If there was change (even a simple change), only the main fetch was called, not the transmit action step. Any thought pls? Thank you.