OpenPostManage runs
Inspect results, resolve failures, and pause or cancel workflow work.
Open Runs and select a run to inspect each step's input, output, result, or error. Open the created post in Publications to check destination delivery.
Pause or stop
- Pause new runs stops automatic starts. Existing runs continue.
- Cancel remaining steps stops the rest of one run. An accepted action may still finish. Created drafts and queued posts remain; manage them in Publications.
- Delete a workflow after pausing it and finishing or cancelling active runs. Deletion removes run history, while created posts remain.
Editing a workflow changes future runs only after you publish it again. Before starting another live run, check whether the previous run created a post or sent a request.
Fix a problem
| Problem | Next action |
|---|---|
| Needs attention on a node | Fill required fields and replace missing variables. |
| No automatic runs | Check activation and source access. GitHub and feeds wait for new items after activation. |
| Waiting for review | Inspect the current post revision and approve it. |
| Stale post revision | Review the latest post and return to the run. |
| Interrupted HTTP request | Check its remote outcome before starting another run. |
| Failed destination | Open the post error and reconnect the account if needed. |
Metrics steps require successful, recent Analytics observations. Missing or stale metrics fail the step rather than becoming zero. Replies use the publishing queue and provider rules.
Reposts
Open a rule under Reposts to change accounts, delays, engagement gates, or repost cycles. Existing rules and per-post overrides remain available. Start from a one-day repost, a one-day and three-day cycle, or a repost after ten likes; new templates start paused.
Enable the rule after choosing accounts. Pause it to stop new reposts; accepted reposts continue. Do not repost and Custom choices on individual posts take precedence.
First comments stay in the post's destination settings. A follow-up workflow sends another reply, so avoid duplicating that comment.
Permissions and limits
Viewers inspect workflows. Editors configure and preview them. Administrators activate workflows, start live runs, test nodes, approve posts, cancel runs, and manage connections. Execution rechecks the activating user's access.
A workflow allows 40 steps and four nested branch levels. A workspace allows 100 workflows and 1,000 active runs. Runs expire after 30 days; the list shows the latest 50. These execution bounds are separate from plan and provider limits.