Restore FileVine-Domo S3 Reporting
Budget: $250 – $750 USD
My FileVine → S3 → Domo pipeline has been silent for roughly a month: nothing is showing up in Domo even though no one touched the FileVine or Domo settings. I need someone who can quickly trace the break, repair it, and verify that the automated reports I relied on are flowing again exactly as they did before.
Here’s what matters to me:
• Identify the root cause of the missing reports—whether the S3 export, the Domo connector, credentials, or schedules are at fault.
• Reinstate the previous reporting schedule so the same data sets appear in Domo without manual intervention.
• Confirm everything is stable by running at least one full cycle and showing the data populating live.
• Provide a brief note (or short Loom) outlining what you fixed so I can reference it later.
You will be working directly in FileVine, AWS S3, and Domo, so familiarity with those tools—especially Domo Workbench and AWS permissions—is essential. If you’ve patched similar pipelines before, that’s exactly the experience I’m after.
Here’s what matters to me:
• Identify the root cause of the missing reports—whether the S3 export, the Domo connector, credentials, or schedules are at fault.
• Reinstate the previous reporting schedule so the same data sets appear in Domo without manual intervention.
• Confirm everything is stable by running at least one full cycle and showing the data populating live.
• Provide a brief note (or short Loom) outlining what you fixed so I can reference it later.
You will be working directly in FileVine, AWS S3, and Domo, so familiarity with those tools—especially Domo Workbench and AWS permissions—is essential. If you’ve patched similar pipelines before, that’s exactly the experience I’m after.