Troubleshooting

This page covers common errors and misconfigurations in Raphtory.

Specifying time measurements

Internally all times in Raphtory are represented as milliseconds using unix epochs. When ingesting data you will need to convert your raw data into the appropriate format. Similarly queries made using the API should use timestamps relative to the unix epoch in milliseconds.

Modeling transactions as state

A common mistake is using PersistentGraph for financial transfers. If A pays B $100 at t1 and you model it as state, the graph will see them as being "in a state of paying $100" forever. Transactions are events – use Graph() instead.

Missing deletions in PersistentGraph

In a PersistentGraph, if you don't call .delete_edge(), every relationship ever created will stay active in your snapshots. Always plan your "end of life" events for persistent data.

Docker graph storage

When saving a graph to disk in the official Docker container, the default location is /home/raphtory_server. This is where the Raphtory server will look for graphs unless you specify an alternative working directory. When saving a file or sending a graph to the server you can always specify a custom path.