Random Unknown Column Exception

This error message is saying that the MySQL database engine cannot find a column named 'ARInvoice.BranchID' in the current context. Generally, when you get an error like this it's because you're trying to select or update a column in a table that doesn't exist, or it's not correctly referenced in your query.

However, in your case, you mentioned the error is intermittent, and a page refresh seems to resolve it. This suggests that the problem may not be with the structure of your database itself, but with how Acumatica is interacting with the database.

A few possible reasons for this could be:

1. Concurrency issues: If multiple operations are trying to access or change the database at the same time, it could potentially lead to inconsistent states where Acumatica tries to interact with a column that isn't currently available. This is more likely if you have a lot of concurrent users or processes.

2. Cache issues: As you suggested, there may be an issue with how Acumatica is caching data. Perhaps there's a bug where it's occasionally caching an outdated or incorrect version of the table structure, leading it to try and access a column that doesn't exist. When you refresh the page, the cache is cleared and the correct structure is loaded.

3. Database connectivity issues: There may be a problem with the connection to your MySQL database, causing intermittent failures when trying to retrieve or update data. A brief network glitch, for example, might cause a single operation to fail while the rest succeed.

It might be helpful to enable detailed logging in Acumatica, if it's not already enabled, to get more information about exactly what's happening when the error occurs. Also, it would be helpful to verify if any database modifications (like triggers, procedures, or scheduled tasks) have been set up that could be causing these intermittent errors.

If you can't identify the issue after investigating these possibilities, I would recommend reaching out to Acumatica's support team for further assistance. The issue may be a bug within Acumatica itself, in which case it will need to be addressed by their development team.