We ran into an issue with our Appian instance and figured out that it stopped wo

Depending on how you cleaned up, you may have ended up with KDBs out of sync since they could not write to disk. Generally, after a full filesystem, it is best to roll back the KDB files to a known-good working state where you have an entire set with the same timestamp.

As a best practice, your developers should be exporting packages of their daily work just to safeguard against environment problems that could cause a loss of data. If they have done so, and you still have a full set of time-matched KDB files from before the out of space problem occurred, I would roll back the KDBs and re-import your applications.

This scenario is why scheduled cleanups are so important. One other thing to keep an eye out for is orphaned active processes resulting from development activity. If your process models don't have a parallel expiration flow you can end up with a few thousand active processes just sitting in memory inflating the size of your KDB files which exacerbates storage problems.

I too would recommend opening a support ticket as you could have underlying object ID mismatches lurking in your KDB files that could cause you problems down the road and will be very difficult to isolate the cause of.

Depending on how you cleaned up, you may have ended up with KDBs out of sync since they could not write to disk. Generally, after a full filesystem, it is best to roll back the KDB files to a known-good working state where you have an entire set with the same timestamp.

As a best practice, your developers should be exporting packages of their daily work just to safeguard against environment problems that could cause a loss of data. If they have done so, and you still have a full set of time-matched KDB files from before the out of space problem occurred, I would roll back the KDBs and re-import your applications.

This scenario is why scheduled cleanups are so important. One other thing to keep an eye out for is orphaned active processes resulting from development activity. If your process models don't have a parallel expiration flow you can end up with a few thousand active processes just sitting in memory inflating the size of your KDB files which exacerbates storage problems.

I too would recommend opening a support ticket as you could have underlying object ID mismatches lurking in your KDB files that could cause you problems down the road and will be very difficult to isolate the cause of.