Strategy Execution Cloud Tracking

What is this?

Every time you execute a pricing strategy in Margin Master (Strategy > Execute Strategy), the application automatically sends a detailed record of the execution to the cloud. This includes a snapshot of each step's configuration and its results -- how many SKUs were affected, what price changes were made, and whether any errors occurred.

This cloud tracking gives your support team full visibility into your strategy history. They can see exactly what ran, when it ran, and what it did -- without needing to be on your machine. It also lays the groundwork for future features like restoring a strategy from a cloud snapshot.

Key behaviors:

• Runs in the background -- Cloud tracking never slows down or delays your strategy execution. It happens after the strategy finishes, in a separate background task.
• Silent on failure -- If the cloud is unreachable (no internet, server down), the strategy still completes normally. A warning is logged locally but nothing interrupts your workflow. Cloud tracking failure never causes a strategy to fail.
• Automatic retention -- Only the last 5 executions per store are kept in the cloud. Older executions are automatically removed.
• Per-step detail -- Each step's full configuration (pricing rule, rounding scheme, Min/Max settings) is captured as a snapshot so support can reconstruct exactly what happened.
• Local logs -- In addition to cloud tracking, each execution writes local log files for offline review (see below).

Local Execution Logs

Each strategy execution also writes two local log files to disk, independent of cloud tracking:

Location: C:\ProgramData\RetailerSoft\MarginMaster\Logs\StrategyExecution\

These files are useful when you need to review a specific execution offline, share results with support, or analyze performance of individual pricing steps. The Query Store analysis section in the detail log is especially useful for diagnosing slow strategy executions.

Who is this for?

• Users -- No action required. Execution tracking is automatic and invisible. You benefit indirectly because support staff can diagnose strategy issues remotely without asking you to reproduce problems.
• Support staff -- Use the Blazor organization dashboard (Events > Strategies tab) to review execution history, diagnose pricing issues, and verify that strategies are running as expected.

How It Works (User Perspective)

1. Execute a strategy normally via Strategy > Execute Strategy
2. After all steps complete, the execution record is sent to the cloud automatically
3. If the upload succeeds, a confirmation message appears in the local log: "Strategy execution tracked to cloud"
4. If the upload fails (no internet, etc.), you will see a warning in the local log but nothing else changes -- your strategy results are unaffected

You do not need to enable, configure, or manage this feature. It is always active.

Blazor Dashboard (Support Perspective)

The organization dashboard has a "Strategies" tab in the Events section.

Master Grid

Shows all executions for the organization with these columns:

Detail Popup

Click any row in the master grid to see the full step-by-step breakdown:

• Rule text -- The human-readable pricing rule that was applied
• SKUs affected -- How many SKUs matched this step and had their future price changed
• Rounding -- Whether rounding was applied and which scheme was used
• No Decreases -- Whether price decrease prevention was enabled
• Min/Max -- Whether Min/Max constraints were active, and impact details (SKUs increased, decreased, unchanged, average adjustment)
• Timing -- How long each step took to execute
• Status -- Success, failure, or skipped

Testing and Verification

User-Side Steps

1. Execute a strategy in Margin Master with at least 2-3 steps
2. Check local logs for the "Strategy execution tracked to cloud" confirmation message
3. Test offline behavior -- Disconnect from the internet before executing a strategy. Verify the strategy executes normally and a warning (not an error) appears in the log

Support-Side Steps

1. Open the Blazor dashboard and navigate to the organization
2. Go to the Events section and select the "Strategies" tab
3. Verify the execution appears in the grid with the correct store, strategy name, and step count
4. Click the execution to open the detail popup -- confirm all steps, configurations, and results are present
5. Execute 6+ times for the same store to verify that the 6th execution triggers trimming (the oldest execution should be removed)

Troubleshooting