Share:

Expected Behaviour of the Remote Event Receiver (RER)

  1. User makes some change on a Sharepoint list, where an event listener is registered (change should trigger workflow start)
  2. Sharepoint sends a change event to the Remote Event Receiver
  3. The remote event receiver forwards this event to the FireStart Server
  4. The FireStart server requests the data from the Sharepoint server
  5. The FireStart server checks, if the start condition is fulfilled and starts the Workflow (as the condition is fulfilled)

Unexpected Behaviour: Workflow does not start

Due to high network latency or high load on the FireStart server, the following scenario can happen:

  1. User makes some change on a Sharepoint list, where an event listener is registered (change should trigger workflow start)
  2. Sharepoint sends a change event to the Remote Event Receiver
  3. The remote event receiver forwards this event to the FireStart Server
  4. User reverts change on the Sharepoint list
  5. The FireStart server requests the changed data from the Sharepoint server
  6. The FireStart server checks, if the start condition is fulfilled and does not start the Workflow (as the condition is not fulfilled)

In this scenario, it can happen that the start condition of the workflow is not valid anymore at the time, the FireStart server received the data from SharePoint.

Unexpected Behaviour: Workflow starts twice

  1. User makes some change on a Sharepoint list, where an event listener is registered (change should not trigger workflow start)
  2. Sharepoint sends a change event to the Remote Event Receiver (event A)
  3. RER cannot reach the FireStart Server, event A will be cached on its disk
  4. User makes some change on the same Sharepoint list (change should trigger workflow start)
  5. Sharepoint sends a change event to the Remote Event Receiver (event B)
  6. The remote event receiver forwards event B to the FireStart Server
  7. The FireStart server requests the data from the Sharepoint server
  8. The FireStart server checks, if the start condition is fulfilled and starts the Workflow (as the condition is fulfilled)
  9. The RER recognizes, that events can be delivered to the FireStart server and sends event A to the FireStart server
  10. The FireStart server requests the changed data from the Sharepoint server
  11. The FireStart server checks, if the start condition is fulfilled and starts the Workflow (as the condition is fulfilled due to the change in event B)




Previous |