wp_uap_recipe_log, wp_uap_trigger_log, wp_uap_trigger_log_meta, wp_uap_action_log, wp_uap_action_log_meta, and the closure log tables. Each can be its own view, or you can build a parent-child setup that links runs to their child triggers and actions in one navigable surface.

Yes. wp_uap_trigger_log_meta stores the values keyed by trigger code. SleekView pivots common keys into columns, like order_id or user_email, and shows the rest in a row-detail panel for inspection. Useful when a recipe fails because the trigger payload didn't include the field the action expected.

Automator itself doesn't have a reviewed flag, so the dimension lives wherever you choose to add it. If you add a custom reviewed column to the log table or store it via add_post_meta on a related post, SleekView reads and writes it as a normal column. The plugin's own log views ignore it because they don't know it exists.

Yes. The recipe log has a completed column with values for in-progress and finished states. Filter on it to find stuck runs, then sort by start time descending to see the oldest ones first. A run that's been in-progress for hours is almost always a hung or failed action that needs investigating.

Yes. Pro uses the same wp_uap_* table family with a few extra metadata fields for premium triggers and actions. SleekView reads whichever tables your install has, so the views don't break if you upgrade or downgrade between Free and Pro tiers.

Each recipe row carries a run_number that increments per execution. SleekView surfaces it as a column so you can sort recipes by total runs and see usage at a glance. A recipe with 12,000 runs is almost certainly mission-critical; a recipe with three runs in six months is a candidate for retirement.

Yes. The action log links to its parent run via the recipe-log foreign key, and the run links to its trigger fires. SleekView's parent-child view follows those links so you start from a failed action row and walk back to the exact triggered payload in one click, no manual ID lookups required.

No. SleekView is read-mostly and only writes when you inline-edit, which is rare on log data. Queries hit indexed columns where Automator has indexes (run_number, completed, date) and cache duration controls keep repeated dashboard loads cheap. The recipe-execution path itself is untouched.