Error Messages

[Developing] This article is the compilation of the error messages that users may encounter in the platform and the corresponding resolution.

 

Error Message: "You can only match transaction from a single day at one time."

Resolution: To represent the cash movement being spread across several days, you would match to the first bank transaction against opening a new balancing item, and then match the second bank transaction against both closing the newly-created balancing item and the withdrawal.

Reference: Titan Support | RE: ***TOP URGENT***PRIORITY OME*** Cash breaks 0.64GBP

 

Error Message: "Totals do not match (XX vs XX)"

Resolution: This normally occurs when manually matching bank transactions. In matching bank transactions, ensure that the transaction amount is equal to the amount that you are matching.

 

Error Message: "Latest price available for asset XXXX is out of date"

Resolution: For exchange-traded assets, the recent-price requirement is that the latest price is no earlier than the previous day (excluding weekends). Typically the platform receives prices from GBO on Sundays, or daily every weekday.

Reference: Titan Support | RE: Priority Two Errored trades Bulk Trades #1234

 

Error Message: "Error in calculation of allowed number of decimals"

Resolution: The client holds this asset to three decimal places because the unit decimal places for this asset has been provided as 3. (validate on Market Data > Update > Fund). To resolve this, you would need to provide updated underlying client allocations for any trades in this asset which have been allocated to more than two decimal places, and then amend the unit decimal places value on the asset page.

Reference: Titan Support | RE: Priority Two Trade Order Issue - GPP003112-00036625

 

Error Message: "Could not place trade TRXXXXXX: Non-success response received from AllFunds API" "H-0200, Amount / units insufficient"

Resolution: This error message is being encountered on a trade in a bulk. The ‘H-####’ format error messages come directly from Allfunds when the platform connects to their API to place the trades. This issue needs to be raised to Allfunds as to why they returned that error for this trade initially.

 

 

Error Message: Session Timeout

Resolution: The platform is currently configured to have a default session expiry time of one hour. Once the session has expired then the user will need to log in again.

Choosing the length of the session expiry time is a balance between security and usability; a shorter expiry may be more secure to users leaving their computer unattended, but result in an active user having to log in more frequently whilst otherwise using the platform.

The session is shared across all tabs within a user’s computer and browser. The session’s expiry time resets whenever a page is loaded, which means that if the user refreshes or navigates within the platform on one tab then the session expiry time for all platform tabs in their browser will be extended.