# CLI Compliance Export Failing

**URL:** <https://forum.mattermost.com/t/cli-compliance-export-failing/10033>\
**Category:** Command Line Interface\
**Created:** [June 30, 2020, 2:58pm UTC](https://forum.mattermost.com/t/cli-compliance-export-failing/10033 "2020-06-30T14:58:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ohgoodgodley](https://avatars.discourse-cdn.com/v4/letter/o/7993a0/32.png) [@ohgoodgodley](https://forum.mattermost.com/u/ohgoodgodley)\
**Post date:** [June 30, 2020, 2:58pm UTC](https://forum.mattermost.com/t/cli-compliance-export-failing/10033/1 "2020-06-30T14:58:40Z")

</div>

I have the Mattermost server running in high availability on two EC2 machines as a service.  
I would like to use the compliance export Beta feature but would like more frequent that once a day if possible.  
I thought about scheduling the cli command, however when i run the cli command, it tries to start a new server, on which it fails (the logs are successfully posted to S3 if i include a timestamp but not registered in the system console as an export job having completed) as it tries to create the ./plugin directory.  
I have these in S3 normally. Is this normal behaviour of the cli? I am using the database to store my config and have passed this is as a flag.

Has anyone had any experience with this?