Scheduled export failes

Q&A
, , ,
1

Schedule fails

There is a gadget whose scheduled export as CSV is not generated.

We have other gadgets on the same dataset in the same dashboard for which schedule exports as CSV work perfectly fine.

We cannot figure out why the schedule export does not work for this particular gadget.

Is there anyone who can give me he hint?

2

Hello @JuliaFee hope this message finds you well!

If I understand well our problem, when a scheduled export as CSV fails for a specific gadget while others on the same dataset and dashboard work fine, there are a few potential causes to investigate according to QS documents

  1. Check the Gadget’s Configuration:

    • Ensure that the gadget (visualization) is properly configured and does not have any unsupported features for CSV export. For example, certain visualizations or calculated fields may not export correctly.

  2. Dataset Permissions:

    • Verify that the dataset used by the gadget has the correct permissions and is accessible by the schedule. If the dataset has restricted access, it might cause the export to fail.

  3. Filters and Parameters:

    • Check if the gadget has specific filters or parameters applied that might be causing the export to fail. For example, if the gadget is filtered to a state where no data is returned, the export might not generate a file.

  4. Data Size and Complexity:

    • If the gadget is working with a very large dataset or complex calculations, it might exceed the limits for scheduled exports. Try simplifying the gadget or reducing the data size to see if the issue persists.

  5. Error Logs:

    • Check the Quick Sight logs for any error messages related to the failed schedule. These logs can provide more specific details about why the export is failing.

  6. Recreate the Gadget:

    • As a last resort, try recreating the gadget from scratch. Sometimes, a configuration issue or corruption in the gadget can cause unexpected behavior.

There is some others support documentations about this topic:

Really hope this suggestions helps you! Please, let me know!

3

Hi @JuliaFee

It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.

If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.

Thank you!

4

Hi @JuliaFee

Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.

Thank you!