Something changed in Production. The application is still running, but the behavior is different.
You check the code.
Everything looks fine.
Then you check the configuration and discover:
`MaximumTransactionLimit = 50,000
But you know it wasn’t always 50,000.`
So the real question becomes:
Who changed the Site Property, when did they change it, and what was the previous value?
This is where OutSystems Service Center becomes surprisingly powerful.
Where to Look
Go to:
Service Center → Monitoring → General Log
Press enter or click to view image in full size
Then search or filter for entries related to Site Properties.
For non-secret Site Properties, the log can provide useful information about the change, including the user who performed it and the previous and new values.
For example:
Site Property:
MaximumTransactionLimit
Old Value:
25,000
New Value:
50,000
Changed By:
admin@company.com
Now you have a much clearer picture of what happened.
Become a Medium member
Instead of:
“The configuration changed, but nobody knows why.”
You can investigate the change directly from Service Center.
Why This Matters
Configuration issues are often difficult to troubleshoot because the application code may be perfectly fine.
The problem might simply be a value that changed in the environment.
That’s why being able to investigate Site Property changes can be extremely useful, especially in Production.
One Important Detail
The Site Property itself is not a permanent version history.
The change information comes from the General Log, which has a limited retention period. So very old changes may no longer be available.
For Secret Site Properties, sensitive values are not exposed in the log.
The Takeaway
When troubleshooting an OutSystems application, don’t only ask:
“What changed in the code?”
Sometimes the better question is:
“What changed in the configuration?”
And Service Center gives you a powerful place to start looking.
Check the value.
Investigate the change.
Find out who made it.
That’s the power of Service Center.

Top comments (0)