# Troubleshooting | CUR enrichment reference Source: https://greenpixie.com/docs/reference/cur-enrichment/troubleshooting What to check when enrichment output does not appear. ## How failures are handled [#how-failures-are-handled] Enrichment runs are monitored by Greenpixie: failed runs alert our team directly and are retried or reprocessed. Nothing is written to your bucket on failure, so the symptom you will see is output not appearing, rather than an error file. If output is missing, work through the checklist below, then contact your Greenpixie representative. ## Checklist [#checklist] ### Directory structure [#directory-structure] The most common cause. Data must either sit in your cloud provider's default export layout, or exactly match the [Greenpixie directory structure](/reference/cur-enrichment/format-and-structure#directory-structure), including the `input` base directory and the `` directory, even when they feel redundant (single platform, dedicated input bucket). Any other custom layout will not be found. Partners must use the partner structure, including the `` and `` directories. ### Permissions [#permissions] Confirm the bucket policy or role assignment from your [platform setup](/reference/cur-enrichment/how-it-works#choosing-your-storage-platform) is still in place: access changes on your side (policy edits, credential rotation, expired client secrets on Azure) are a common cause of silently stopped enrichments. ### File size and format [#file-size-and-format] Partitions must be under **500MB** each, in a [supported format](/reference/cur-enrichment/format-and-structure#data-format). If your data involves a very large number of files per month, mention it to your Greenpixie contact so the run can be sized accordingly. ### Partner triggers [#partner-triggers] If you are a partner and an upload has not been processed, confirm the `.upload_finished` file was written into the `` directory **after** all partitions finished uploading. Marked uploads run in the nightly check between 01:00 and 04:00 UTC, so one marked after 03:00 UTC may wait until the following night. If you set up on-demand runs on S3, also check that the bucket's event notification targets the SNS topic ARN we provided; see [Partner trigger](/reference/cur-enrichment/partner-trigger). ## Still stuck? [#still-stuck] Contact your Greenpixie representative with the bucket/container name, the directory path you expected output for, and roughly when the data was uploaded; we can check the run logs from our side.