Sign in

Replication Transactions Not Being Created

March 9, 2026 01:24 AM
1 min read
  • If replication transactions are not being created for a file, either an event to trigger checking of the replication rules has not occurred, or the file does not match the criteria set for any active replication rule. Another rare potential cause is that one or more of the vault servers have not been upgraded to the same Aras Innovator version as the main server.
  • Confirm that the installed version of Aras Innovator on each vault server is the same Aras Innovator version as the main server.
  • Determine the rule which should have triggered a replication transaction and confirm it is Active.
  • Confirm the file exists in the Vault where that rule is defined, and matches a file type in the File Type Filter for that rule, if any are specified.
  • Confirm that a copy of the file does not exist on the vault(s) to which the file should replicate.

  • For an onChange rule –

    The most common reason for an onChange rule not to execute is that file was saved to a vault which does not have a matching onChange rule. Based on the User who saved the file, confirm a matching onChange rule exists on the Vault for that User’s Default Vault.

  • For an onDemand rule –

    The most common reason for an onDemand rule not to execute is that the file was retrieved for the user from a different vault than one with the rule. Aras Innovator gets the file based on where the file exists, and selects the vault based on the Read Priority, then Default Vault of the user, or from any other vault. So if the file is retrieved from a vault which does not have an applicable onDemand rule, instead of another vault with such rule, no replication transaction is created.

  • For an onEvent rule –

    Confirm that the method written to call the replication request actually executes. If so, confirm that a copy of the file with the file ID specified by the method exists on the vault with the onEvent rule. This may be done by viewing the file as a user configured with that vault as its highest Read Priority, then noting the vault which actually returned the file through the URL of the viewer, or by an AML nash or other query of the Located relationship(s) for the file.