Official Content

In the Offline Native Mobile Applications, when there is a Synchronization.Send() operation, the device sends to the server a list of Business Component (BC) operations which were performed localy. The server then applies these operations to the central database.

There are some cases where a BC operation can result in an error for several reasons: business rules which succeded in the device but failed on the server database, referential integrity, etc.

How changes are applied to the server

There is a procedure, called "OfflineEventReplicator", which handles the list of operations sent from the device.

The signature of this procedure is as follows:

parm(in:&GxPendingEvents, in:&GxSyncroInfo, out:&EventResults);


  • &GxPendingEvents are the events sent by the device,
  • &GxSyncroInfo contains additional information required by the synchronization process, and
  • &EventResults is a collection of the results of each pending event processed by the server.

How errors are handled

The GeneXus developer might need to have control over the behavior of the application whenever there is an error in a Send operation.

There are two procedures, called automatically from the OfflineEventReplicator procedure, which notify the application of any error and allows the programmer to take any required action.

These procedures are located in the GeneXus\SD\Synchronization folder under the Root module of the Knowledge Base. Note that they are not inside the GeneXus Module, because they may be modified locally in the KB.


This procedure is called on every BC operation that finishes with an error.

The signature of this procedure is:

parm(in:&PendingEvent, in:&BCName, in:&BCJson, in:&EventResult, in:&GxSyncroInfo, out:&Continue);


  • &PendingEvent is based on GxSynchroEventSDT.GxSynchroEventSDTItem and has the information about the failed event,
  • &BCName is a VarChar(128) and contains the name of the business component,
  • &BCJSon is based on EventData and contains the BC's JSON representation associated with the failed event,
  • &EventResult is based on GxSynchroEventResultSDT.GxSynchroEventResultSDTItem and has the information about the nature of the failed event (fields: EventStatus and EventErrors),
  • &GxSynchroInfo is passed along from the OfflineEventReplicator procedure, and
  • &Continue is a Boolean which indicates if the OfflineEventReplicator procedure should continue processing the next items (return True) or if it must abort the synchronization (return False).

By default, this procedure is empty (except for the assignment &Continue = True) so that the GeneXus developer can indicate the action to take under each circumstance.


This procedure is called by the OfflineEventReplicator before processing any of the BC operations.

Its signature is the same than the one of the OfflineEventReplicator.

You can change this procedure by adding log information or even change, with caution, the list of events to be processed.

Note: This procedure is available since GeneXus 16 upgrade 1.

Warning: For already existing KBs, migrated from previous GeneXus versions, this procedure must be imported from <genexus_installation_directory>\Packages\Patterns\WorkWithDevices\Resources\SDApi.xml .


This procedure is called after processing all the BC operations, whether all operations completed successfully or there were any errors. It is called even if a call to the GxOnPendingEventFailed procedure finished with &Continue = False.

The signature of this procedure is:

parm(in:&EventResults, in:&GxSyncroInfo);


  • &EventResults is based on GxSynchroEventResultSDT, which is, the collection returned to the device and has all the information about the synchronization result, and
  • &GxSynchroInfo is passed along from the OfflineEventReplicator procedure.

Last update: November 2023 | © GeneXus. All rights reserved. GeneXus Powered by Globant