# Expose compound action execution log to aid debugging

**URL:** <https://community.glideapps.com/t/expose-compound-action-execution-log-to-aid-debugging/22971>\
**Category:** Feature Requests\
**Created:** [February 18, 2021, 8:58am UTC](https://community.glideapps.com/t/expose-compound-action-execution-log-to-aid-debugging/22971 "2021-02-18T08:58:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [February 18, 2021, 8:58am UTC](https://community.glideapps.com/t/expose-compound-action-execution-log-to-aid-debugging/22971/1 "2021-02-18T08:58:32Z")

</div>

One thing I have found is that when compound actions fail, they fail _silently_, with no feedback whatsoever. This can make them extremely difficult to debug - especially more complex ones.

It would be great if we could enable and access some sort of debug/execution log, so the point of failure could be more easily pinpointed.