Sometimes you will set up a new instance of a CircleCI self-hosted server, and although your commits are going through, you will see a "No Workflow" message for your build. This is relatively common and easy to address.
- The first and most common is that your nomad pods are failing and need to be restarted.
- The next possible option is that your S3 permissions are set for only read access, or simply do not have the correct permissions required to access the bucket at all. You can find the full policy.json required, here on our documentation site.
If you have attempted all of these solutions and still do not see a positive change in behavior, please feel free to reach out to our Support team.