Scheduled report emails go out even when the collection behind them has failed, so recipients receive half-filled numbers. In this case, the immediate task is to prepare scheduled report delivery after successful refreshes. The workflow should produce an automation specification and sample report structure noting each dependency and fallback action.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me prepare scheduled report delivery after successful refreshes.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [recipients and their roles, delivery cadence and send time, accepted report formats and attachment limits, and the refresh and validation steps each send depends on with expected completion times]. Gate every send on a successful refresh and a passed validation so no delivery publishes an incomplete collection, holding the send when a dependency fails and triggering the fallback action stated for that dependency instead of releasing the previous figures as if they were current.
Return an automation specification and sample report structure noting each dependency and fallback action for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Collect the recipients and their roles, the delivery cadence and send time, the report formats and attachment limits accepted by the mail system, and the refresh and validation steps each send depends on with their expected completion times.
Gate every send on a successful refresh and a passed validation so no delivery publishes an incomplete collection, holding the send when a dependency fails and triggering the fallback action stated for that dependency instead of releasing the previous figures as if they were current.
Deliver the automation specification and sample report structure noting each dependency and fallback action, then verify by checking a recent send against the run log, confirming that the attachment passed validation before release, that failures notified the owner with a reason and that no recipient received a report built on a failed refresh.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Yes, and for the validation that follows it. A send released early publishes figures from a collection that never finished, and recipients cannot tell the difference because the message looks exactly like a complete one, only with lower numbers.
The send is held and the owner receives the failure reason and the affected period, rather than a report repeating last period's figures behind a current date. Recipients get a short note saying no report is coming and why.
Enough to interpret the attachment: period covered, refresh time, any provisional period and the main movement. The full structure stays in the file, so the body never becomes a second copy that drifts from the attachment after the first edit.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.