Hey there!
For one of our team members, after-update trigger does not seem to run (he can manually execute the script that’s in the trigger). I’d like to debug this, see if the script is actually run, what’s the exit code, etc - but whatever I try, I’m unable to get debug logs to show the triggers that are found / run (even on a machine where it runs properly - there’s no mention of them whatsoever afaict).
Can I somehow make Plastic log this (maybe via some plastic.log.conf magic)?
Thanks!
Hi @KristofMorva ,
Please ask the user to open a ticket with the UVCS support team. This issue can be caused by many different reasons.
Hey @rednbrick! Thank you, but at the moment I’m not seeking out support regarding the issue itself, I’m mainly looking for ways to get triggers to show up in the log so that we can track it down whenever it happens 
The client log should have information on trigger execution.
You can find the client log at
Windows path: %localappdata%\plastic4\logs\
Mac/Linux path: $HOME/.plastic4/logs/
You can ask the user to create a trigger with the same type of script trigger that intentionally failed and check if the trigger ever fails. This way, you can see if Plastic SCM is accessible to the script. what types of script do you use for the trigger? sometimes, the environment variable of the PC that runs triggers also matters.
Hey! Unfortunately I can’t see anything like that there. I have zipped up the log on a machine where I have deliberately synced so that the post-update trigger would run (and I have visually seen it running). Am I blind or the execution is not in the logs? 
This is how the script looks like: powershell -ExecutionPolicy Bypass @WKSPACE_PATH/Build/Engine/DownloadEngine.ps1
Hi @KristofMorva,
Please open a support ticket with us. Please share how you have run the trigger.
Hey, sorry for the delay, I think we’ve figured it out - client side triggers don’t seem to run in Gluon.
Are there any plans to make them work? (or, if they should work, then I’ll create the support ticket 
)
Hi,
Based on this link, Triggers guide · Plastic SCM version control
Gluon should also run the trigger.
