How to Run and Troubleshoot Automations in Mydrop

By the end of this tutorial you will be able to run a saved automation in Mydrop, confirm it completed, and fix common configuration issues so your repeatable social publishing runs reliably.

Open the Automations area from the main navigation to follow along. The Automations list shows saved automations and controls such as New Automation, Run once, Pause, Duplicate, Edit, and Delete. This section prepares you to verify permissions, content, and schedule before running or testing an automation.

Before you start

Checklist

1. Workspace access and permissions

   • Confirm your account has permission to view and run automations in the workspace.
   • If the automation needs approval, confirm approver accounts are available and invited.

2. Target profiles or groups

   • Identify the profile or profile group the automation will publish to.
   • Verify each target profile is active and connected to the platform you intend to post to.

3. Required media and captions

   • Upload any images, videos, or attachments you plan to post.
   • Write and save captions, including platform-specific fields (example: alt text, link previews, hashtags).
   • For tests, prepare a small set of media and a short caption so runs complete quickly.

4. Platform-specific requirements

   • Check platform limits (image size, video length, caption length) and ensure your content meets them.
   • Add any required fields for the target platform before running.

5. Timezones and schedule checks

   • Confirm your workspace time zone and the intended posting time.
   • For scheduled automations, verify the schedule uses the expected time zone to avoid off-hour posts.

6. Approval and notification settings

   • If the automation requires post approval, ensure approvers are assigned.
   • Confirm notification channels (email or workspace notifications) are configured so you get success or error alerts.

7. Automation state and saved edits

   • Open Automations and find the automation you want to run.
   • Make sure the automation is saved and not left with unsaved edits.
   • Ensure the automation is not paused if you intend to run it immediately.

Quick preflight steps

1. Open Main nav > Automations and locate the automation row you will test.
2. Click Edit to open the builder and quickly confirm profiles, caption, media, trigger, and options are set.
3. Save any edits, then return to the Automations list and confirm the row updates (status, last run, next run).

Why these checks matter

• Missing captions, required platform fields, or media are the most common reasons a run fails.
• Running with the wrong profile or in the wrong time zone leads to posts going live where or when you did not expect.
• Unsaved edits or a paused automation prevent a run from executing even when other settings are correct.

What you should see before proceeding

• The Automations list shows the saved automation with a clear status (active or paused) and recent run metadata.
• Media and caption previews present in the builder match the content you intend to publish.
• Approvers and notification options are visible when the automation requires them.

Proceed to the automation run steps only after the checklist items are green. This reduces the chance of errors and makes validation faster when you run the automation or perform a test Run once.

By the end of these steps you will have opened Automations and created the basic settings for a saved automation that is ready to run or edit.

Step 1: Open the feature

1. From the main navigation, click Automations.

   • What to expect: the Automations page appears with a list of saved automations and a prominent New Automation button.

2. Locate the New Automation button and the saved-automations list.

   • What to click: New Automation to start a new workflow.
   • What to check: the list shows rows for existing automations with columns for name, status, last run, next run, and actions.

3. Scan the automation row controls.

   • What you will see: action controls such as Run once, Pause, Duplicate, Edit, and Delete visible on each row or within a row menu.
   • Why it matters: these actions let you test, pause, copy, modify, or remove an automation without opening the builder.

4. Open an existing automation for a quick look (optional).

   • What to click: Edit or the automation name in the list.
   • What to see: the automation opens in the builder where steps and saved values are visible. This confirms you have permission to view and edit the automation.

5. Verify page-level indicators and status.

   • What to look for: status labels (Paused, Active), a last-run timestamp, and any brief error or warning indicators shown in the list.
   • Expected result: the Automations list shows at least one saved automation or the New Automation button if none exist.

Step 2: Set up the basics

Quick checklist before building (one-line checks)

• Confirm you have permission to run or edit automations in your workspace.
• Confirm target profiles or profile groups exist and are selected.
• Ensure required media and captions are available for the post.

1. Start a new automation.

   • What to click: New Automation on the Automations page.
   • What to see: the builder opens and prompts you for a name and basic choices such as profiles, trigger type, and schedule.

2. Name the automation and choose target profiles or a group.

   • What to enter: a clear name that describes the workflow (for example, Weekly Promo Posts).
   • What to choose: one or more profiles or a predefined profile group.
   • What to check: selected profiles appear in the builder summary; if none are shown, pick at least one before saving.

3. Select a trigger type.

   • What to choose: a time-based schedule (for recurring runs) or an event trigger if available.
   • What to check: fields for frequency, date ranges, and time zone. Make sure the schedule matches the timezone you intend to publish in to avoid timing mistakes.

4. Configure the schedule or event details.

   • What to set: interval or exact date/time for the trigger, and any hourly/day/month options that appear.
   • Why it matters: incorrect frequency or timezone is a common cause of missed runs. Confirm Next run or schedule preview if the builder shows it.

5. Save the basic settings.

   • What to click: Save, Save Draft, or the builder Continue/Next button until you return to the main builder summary.
   • What to expect: the automation appears in the Automations list with the name you entered and a status such as Active or Paused depending on your choice.

6. Quick verification after save.

   • Where to look: the saved automation row in Automations.
   • What to see: the name, chosen profiles, status, and a Last run field (empty for new automations) or Next run date if scheduled.
   • What to do if you do not see expected values: open Edit to confirm profiles, trigger, and that the automation was saved successfully.

7. Optional: set the automation to Run once for a test.

   • What to click: Run once from the automation row.
   • Expected result: a run starts immediately and the row will update with run status or a reference to logs. Use this to confirm the basic setup works before adding content.

Conclusion hint: after completing these basic steps, proceed to add content, media, and notifications in the builder, then run a test run and check run details to confirm successful publishing.

After this step you will have added captions, media, platform options, and notification settings to a saved automation and learned how to save, preview, and run it for verification.

Step 3: Add the content or settings

Short checklist before editing content:

• Target profiles or group selected.
• Media files uploaded to the workspace or profile library.
• Captions and platform-specific fields prepared.
• Approver(s) identified if approval is required.

1. Open the saved automation and go to the content step.
2. Add the primary caption or post text.
   • Click into the caption box and paste or type the final copy.
   • For multi-platform automations, check each platform tab and adjust captions if platform limits or formatting differ.
   • Check: the caption area should not display a required-field error when complete.
3. Attach media.
   • Click Add media and choose images or video from the workspace library or upload new files.
   • Confirm each selected file shows a thumbnail or filename in the media area.
   • Check: platforms that require media will show an alert if no media is attached.
4. Configure platform-specific options.
   • For each destination (for example, Instagram, Twitter/X, Facebook), open its options and set required fields such as link previews, alt text, or card settings.
   • If the platform offers scheduling options in the builder, verify the chosen schedule matches your time zone and posting window.
   • Check: the UI should show platform validation messages if something is missing or invalid.
5. Set notifications and approvals.
   • Enable notifications or add approvers if the automation needs review before posting.
   • Choose workspace members or approver groups and confirm the approver list saves.
   • Check: an approver requirement should be visible in the automation summary and will block runs until approved.
6. Configure repeating options or post frequency if the automation should publish periodically.
   • Select interval or schedule options and confirm the next run time updates in the preview area.
   • Check: ensure the interval is not in conflict with platform rate limits or workspace posting windows (the UI will flag obvious conflicts).
7. Save the content step.
   • Click Save or Save and Continue depending on the builder.
   • Wait for the filled or saved indicator to appear (for example, a confirmation message or a filled loading icon).
   • Check: unsaved edits will typically show a draft or unsaved marker. Confirm it disappears after saving.
8. Preview the assembled post.
   • Use the Preview button if available to see how the post will render for each platform and profile.
   • Verify caption length, media display, and any platform cards or link previews.
   • Check: preview should match what appears in the calendar or a single-run test.

Tip: If unsure which field is required, attempt a Run once test (Step 4) to surface validation messages quickly.

Step 4: Review the workflow

Outcome: confirm the automation row shows correct status and last-run details, and inspect run logs to verify success or find actionable errors.

1. Return to the Automations list.
   • Locate the automation row you edited.
   • Confirm the status column shows Active, Paused, or Draft as expected.
   • Check: the row should display a next-run time or last-run timestamp after a run.
2. Run a quick test using Run once.
   • Click Run once for a one-time execution to validate settings without changing the saved schedule.
   • Check: run status should update to Running then to Success or Failed within the run details link.
3. Open run details or logs.
   • Click the run or last-run link in the automation row to view run output.
   • Look for success confirmations or specific error messages such as missing captions, media failures, permission errors, or approval blocks.
   • Check: the log should identify which profile or platform failed so you can edit only the affected items.
4. Resolve common errors and re-run.
   • Wrong profile selected: edit profiles and Save.
   • Missing caption or platform field: add the field and Save.
   • No media uploaded where required: attach media and Save.
   • Timezone or schedule mismatch: adjust schedule and confirm next-run time.
   • Paused automation: toggle to Active and Save.
   • Check: after each fix, use Run once to confirm the specific error no longer appears.
5. Use Duplicate for safe edits.
   • If you need to try larger changes, Duplicate the automation and test on the copy.
   • Check: the duplicate should inherit content and settings but allow edits without impacting the live automation.
6. Confirm notifications and approvals.
   • Check that notification recipients receive the expected alerts after a successful run or approval request.
   • Check: approvers should see the pending item in their workspace notifications until they approve.

Final verification: the automation row shows a recent successful last-run entry or a scheduled next-run, and the run details/logs show success messages or clear, actionable errors that were resolved.

Troubleshooting and next steps

After completing these steps you can run a saved automation, confirm its result, and fix common configuration issues so the automation runs reliably. Use this checklist and step-by-step fixes when a run shows errors or does not publish.

Quick checklist before troubleshooting

• Confirm the automation is saved and not paused.
• Confirm the correct profile or profile group is selected.
• Confirm required media is uploaded and captions/platform fields are filled.
• Know the automation time zone and scheduled time.
• Confirm you have workspace permission to run or edit the automation.

Step-by-step troubleshooting

1. Run a test run (Run once)

   1. From Automations, locate the saved automation row and click Run once.
   2. Expect: the UI shows a running state and then a status update in the row (success or failure).
   3. If nothing happens, confirm the automation is saved and not paused, then try Run once again.

2. Check run status and logs

   1. Open the automation row details or the run history link.
   2. Look for a clear success message or a specific error message in logs.
   3. Verify the last-run timestamp updates and any error text explains which field failed.

3. Fix a wrong or empty profile selection

   1. Edit the automation.
   2. Re-select the target profile or profile group from the profiles step.
   3. Save, then Run once. Expect the run to target the chosen profiles and show success for each profile.

4. Resolve missing caption or required platform fields

   1. Edit the automation content step.
   2. Add the caption and complete platform-specific options (for example: post type, link preview options).
   3. Save and Run once. Expect success; if the run still fails, the log will list the missing field.

5. Add required media

   1. Edit the automation and upload the required images or videos in the media step.
   2. Save and Run once for a test.
   3. If a platform requires a specific media type, confirm the file format and size meet the platform prompt before re-running.

6. Fix timezone or schedule mismatches

   1. Edit the trigger or schedule step and confirm the automation time zone and scheduled time.
   2. If a scheduled run seems off, adjust the time or run a Run once test to validate immediate behavior.
   3. Expect the next-run column in Automations to match your updated schedule.

7. Address paused automations and unsaved edits

   1. Check the status column: if Paused, click to resume.
   2. If edits were made but not saved, re-open the automation, finish required fields, and click Save before running.
   3. Expect saved edits to appear in the automation row and be used on the next run.

8. Confirm workspace permissions and approver settings

   1. If a run fails with an authorization or approval error, confirm you have run/edit rights for the workspace.
   2. If the automation requires approval, check the configured approver(s) and whether they received the review request.
   3. Fix approver settings or request the necessary permission, then re-run.

Quick fixes for common error messages

• "No profiles selected" - Edit and pick profiles or a profile group; save.
• "Missing caption or required field" - Add the missing text in content step; save.
• "Media required" - Upload acceptable images/videos and save.
• "Scheduled time mismatch" - Verify time zone and schedule, then resave.
• "Paused" - Toggle the automation to active and run a test.
• "Insufficient permissions" - Ask a workspace admin to grant run or edit access.

Next steps after a successful fix

1. Duplicate the automation to make safe edits and test changes without affecting the original.
2. Use Run once to validate edits before scheduling.
3. Monitor the Automations list for next-run and last-run status.
4. Keep a short run log in calendar notes or project notes for recurring troubleshooting context.
5. Confirm recipients of notifications or approvals actually received requests (email or message channels).

Conclusion

After applying these checks and fixes you should be able to run an automation, read the run status and logs, correct configuration errors, and re-run successfully. Use Run once, duplicate for safe testing, and monitor the Automations list to keep repeatable publishing reliable.