How to Pause, Duplicate, and Run Automations in Mydrop

By the end of this tutorial you will have a saved automation in Mydrop that you can pause, duplicate, run once, and edit so your team can safely test and reuse a repeatable publishing workflow.

Before you start

Checklist

1. Confirm permissions and notifications

   • Make sure your workspace role allows creating and managing automations.
   • Verify notification settings so you receive run and error alerts for automations you control.

2. Prepare target profiles or groups

   • Choose the profile(s) or group the automation will post to.
   • Have profile selection details at hand; Mydrop validates profile choices before scheduling.

3. Gather post content and media

   • Prepare captions and any images or video files you plan to publish.
   • If using Google Drive, ensure the Drive connection is available in Gallery so you can import media directly.

4. Note platform-specific requirements

   • Be ready to supply platform fields such as thumbnails, duration, or category when required.
   • Mydrop performs pre-publish validation that checks captions, media format, size, and platform fields.

5. Plan your trigger and schedule

   • Decide whether the automation uses a time-based schedule, interval, or another trigger type.
   • Have start dates, repeat intervals, and time windows noted.

Quick navigation reminder

• From the main navigation, open Automations.
• Use the New automation button to create a new workflow or select an existing automation to open its detail view.

What to save and why it matters

• Save early and often in the builder. Unsaved changes are not applied when you run or duplicate an automation.
• Saving locks in profile selections and trigger settings that Mydrop validates before allowing a scheduled run.

What validation will check

• Profile selection: at least one valid profile or group must be chosen.
• Captions and media: checks for required text and supported media formats.
• Dates and times: ensures schedule values are complete and not conflicting.
• Platform fields: verifies platform-specific inputs (thumbnails, duration, categories) are present when required.

Pre-checks for a successful run

• Confirm you can import the selected media into the Gallery (use Google Drive import if needed).
• If you plan to Run once for testing, prepare a test profile or a non-public time slot to avoid accidental publishing to live audiences.
• Verify that teammates who need visibility have notification and permission settings configured.

Short troubleshooting pointers you can address now

• If you cannot save an automation, check workspace permissions.
• If media import fails, reconnect Google Drive in Gallery and re-select files.
• If validation flags missing inputs, complete the highlighted fields before proceeding.

Ready indicator

• You are ready to proceed to the automation builder when:
  • You can open Automations from main nav and click New automation.
  • You have at least one target profile or group selected.
  • Required media and caption are available and pass pre-publish validation locally.

Next

• Open Automations in the main navigation and click New automation (or open an existing automation) to begin step-by-step setup in the builder.

The automation is saved and ready so the team can pause, duplicate, run once, or edit it from the Automations list.

Step 1: Open the feature

1. From the main navigation, click Automations.
2. On the Automations page, click New automation to start a fresh automation.
3. To edit an existing automation instead, find its row in the Automations list and click its name or the row to open the automation detail and builder. Use any search or filter controls on the page to locate the automation if you have many entries.

Checklist before continuing:

• Confirm you opened the Automation builder screen (a header or step indicator for the builder should be visible).
• If opening an existing automation, confirm the builder shows the automation name and current status.

4. After clicking New automation or opening an existing item, you should see the builder interface with labeled sections for profiles, trigger, content, media, and options. The screen typically shows fields to name the automation, select profiles or groups, and choose a trigger type.
5. If the builder does not appear, check browser popups or reload the Automations page, then repeat step 2 or step 3.

What to look for after opening:

• A visible name field or title at the top of the builder.
• A Profile or Group selector area where chosen profiles display as chips or badges.
• A Trigger type selector or dropdown so you can choose how the automation runs.

Step 2: Set up the basics

1. Name the automation.

   • Click the Name field at the top of the builder and enter a clear name that describes the workflow (for example, "Weekly Promo Post - Instagram").
   • A meaningful name helps teammates find and duplicate this automation later.

2. Choose profile(s) or a group.

   • Click the Profile or Group selector.
   • Pick one or more profiles or a preconfigured group.
   • After selection, confirm the chosen profiles appear as visible chips, badges, or a list in the builder.
   • Important: If no profiles are selected, Mydrop will block scheduling later; ensure at least one profile is chosen now.

3. Select the trigger type.

   • Find and open the Trigger type dropdown or section.
   • Choose the trigger that matches your workflow: for example, scheduled intervals, specific date/time, or an external trigger if available.
   • After selecting a trigger, the builder will reveal additional schedule controls (frequency, date, time, or interval). Confirm those controls appear.

4. Configure schedule options.

   • For a one-time schedule, choose a date and time. For recurring workflows, set frequency and time window.
   • Use the time picker or interval controls to set exact posting windows.
   • Confirm the schedule summary or preview updates to show the selected run times.

5. Save the basics.

   • Click Save or Save Draft at the bottom or top of the builder to persist these initial settings.
   • After saving, look for a confirmation message, toast, or banner that states the automation was saved.
   • The automation should now appear in the Automations list with its name and current status.

Quick verification checklist:

• The automation name appears in the builder and in the Automations list.
• Selected profiles display as chips or badges in the builder.
• The chosen trigger and schedule values are visible in the builder and summarized in the list row or detail view.
• A save confirmation appeared and the automation row is present in the Automations list.

What to expect next:

• The automation is now saved with its basic configuration. From the Automations list or the automation detail view you can Pause, Duplicate, Run once, or Edit the automation. Status and notifications will reflect future changes, and Mydrop will apply pre-publish validation when you add content or schedule posts.

If something went wrong:

• If profiles did not save, reopen the builder, reselect them, and save again.
• If the schedule controls did not appear after selecting a trigger, reselect the trigger type so the builder reveals the correct schedule options.
• If Save fails, check your workspace permissions and retry.

Step 3: Add the content or settings

After completing these steps the automation will have captions, media, post options, and pass pre-publish validation so it can be run once, duplicated, paused, or edited.

Checklist before adding content

1. Profiles or group selected from Step 2.
2. Captions and media files ready (or available in Google Drive).
3. Any platform-specific fields identified (links, thumbnails, categories).

Steps to add content and run validation

1. Open the automation detail in the builder and go to the content section.
2. Add the caption or post text in the caption field. Type or paste the final copy exactly as you want it published.
3. Add media:
   • Click the Gallery button to choose existing media.
   • To import from Google Drive, choose the Drive import option in Gallery, connect your Drive if prompted, select files, and confirm. The selected files should appear in the automation gallery.
4. Choose post options and platform-specific fields:
   • Set options such as link previews, thumbnails, board or category if shown.
   • Fill any required platform-specific inputs (for example, thumbnail selection for video or duration for platform rules).
5. Attach scheduling or trigger details if the automation includes timed runs. Confirm the trigger settings match the desired test or live run.
6. Click Save to store the changes. Saving keeps the automation in the Automations list and updates the automation status.
7. Run pre-publish validation:
   • Click the Review or Validate button (often shown as Review/Preview).
   • Read any validation messages shown. Mydrop checks profiles, captions, media types, sizes, and platform fields.
8. Fix issues flagged by validation, then repeat the validation step until no blocking errors remain.

Verification checks for content and settings

• Caption check: Validation should not show "missing caption" or related errors.
• Media check: Images or videos should show as attached in the builder and not be marked incompatible.
• Drive import check: Files imported from Google Drive appear in the gallery preview.
• Platform fields check: Any required platform-specific inputs are marked complete by validation.
• Save check: The automation shows a saved state or confirmation message after clicking Save.

Quick troubleshooting tips

• If validation keeps failing for media, re-upload the file in a supported format.
• If Drive import does not appear, reconnect Drive and re-import the file in Gallery.
• If a required field is unclear, open Review/Preview to view the list of missing items.

Step 4: Review the workflow

After reviewing the workflow the automation should be ready to pause, duplicate, run once, or edit from the Automations list or its detail view.

Steps to review and control the automation

1. Open the Automations page and locate the automation row or open its detail view.
2. Click Review or Preview to see a final summary of content, profiles, schedule, and validation status.
3. Confirm status:
   • The automation status should be Active, Paused, or Saved depending on prior actions.
   • Validation should show no blocking errors if you intend to run or schedule.
4. Use lifecycle controls from the row or detail view:
   • Pause: Click Pause to stop scheduled runs. Confirm the status updates to Paused and notifications reflect the change.
   • Duplicate: Click Duplicate to create a copy. Open the duplicate to confirm name, profiles, and content are copied and editable.
   • Run once: Click Run once to execute a single test run. Watch for an on-screen confirmation or activity message and any sent notifications.
   • Edit: Click Edit to return to the builder and make changes. Save and re-validate after edits.
5. After using Run once, check notifications or activity logs that confirm the run occurred. The automation should remain in the saved state unless you change it.

Verification checks after review

• Pause verification: Automation row shows Paused and scheduled runs are suspended.
• Duplicate verification: A new automation appears in the list with a distinct name or copy suffix and opens for editing.
• Run once verification: A confirmation appears and notifications are sent to configured recipients; the automation content must match the preview.
• Edit verification: Changes are saved and validation passes again.

Common mistakes to avoid

• Trying to run or duplicate without saving recent edits.
• Ignoring validation messages that block publish or run.
• Not selecting profiles or groups before running.
• Lacking permission to perform Pause, Duplicate, or Run once actions; confirm workspace permissions if controls are unavailable.

Conclusion Once validation passes and the automation appears in Automations with the expected status, use Pause, Duplicate, Run once, or Edit from the list or detail view to safely test and reuse the workflow.

Troubleshooting and next steps

This section helps recover from common problems and shows practical next steps to verify your automation is working as expected.

Quick checklist before troubleshooting

1. Confirm the automation is saved and the UI shows a saved status or confirmation.
2. Check that profiles or groups are selected.
3. Re-run pre-publish validation and note any error messages.
4. Verify you have permission to edit, duplicate, or run automations.

Common fixes (step by step)

1. Validation errors prevent Run once or scheduling

   1. Open the automation in Automations.
   2. Click Review or Preview to surface validation messages.
   3. Address each item shown (profiles, caption, media, date/time, platform-specific fields).
   4. After fixing, click Save and run Review again until no validation errors appear. Result: validation clears and Run once or Schedule becomes available.

2. Missing profiles or groups

   1. Edit the automation and go to the profiles or audience step.
   2. Select one or more target profiles or a group from the list.
   3. Save the automation. Result: selected profiles are listed on the automation row and pre-publish checks include those profiles.

3. Unsupported or missing media

   1. Open the Media step and confirm media thumbnails appear.
   2. If a file is missing or rejected, re-add it from Gallery.
   3. To import from Google Drive: open Gallery, use the Drive import, choose the file, then attach it to the automation.
   4. Save and re-run validation. Result: media shows in the automation and passes size/format checks.

4. Run once button disabled or Run fails

   1. Ensure the automation is saved and passes validation.
   2. Confirm your workspace role allows running automations.
   3. If Run once still fails, check in-app notifications for the failure reason and fix any listed issues, then retry. Result: Run once completes or provides a clear error message to correct.

5. Duplicate not appearing or duplicates have same content

   1. From the Automations list, click Duplicate on the source automation.
   2. Refresh the Automations list or search for the duplicated name (the copy often includes "Copy" or a timestamp).
   3. Open the duplicated automation, update name, content, or schedule, then save. Result: a new editable automation row appears; you can modify and validate it independently.

6. Pause and resume not updating status

   1. Use Pause on the automation row or detail view.
   2. Confirm the automation status label changes to Paused.
   3. If status does not change, refresh the Automations list and check notifications for permission or conflict messages. Result: paused automations stop scheduled runs until resumed.

Verification checks

1. Confirm automation status updates in the Automations list after each action (Paused, Active, Draft).
2. After Run once, check Calendar or recent activity to confirm the test publish or scheduling attempt is recorded.
3. For duplicates, confirm the new automation is editable and shows its own validation state.
4. Check in-app notifications or your workspace notification settings to see alerts about runs, failures, or approvals.

Next steps for safe testing and reuse

1. Test with a single staging profile first: use Run once to validate the end-to-end publish without affecting all profiles.
2. Duplicate for variations: create separate copies for A/B content or scheduling changes, then edit and validate each copy.
3. Use Pause while reviewing: pause automations you do not want to run while teammates review changes.
4. Keep notes and context: add a calendar note or a conversation thread to explain why an automation was paused or duplicated.
5. Confirm team visibility: ask teammates to check Automations and notifications to ensure permissions and alerts work as expected.

If problems persist after these checks, gather the automation name, status shown in the UI, validation messages, and which action failed (Pause, Duplicate, Run once, Edit). Share those details with your workspace admin so they can verify permissions or workspace settings.

Conclusion

Following these troubleshooting steps will help resolve the most common issues with pausing, duplicating, running once, and editing automations. After fixes, the automation should save, show the correct status, and pass pre-publish validation so Run once and scheduling work reliably. Use duplication and Pause to test and iterate safely before rolling changes out to the full team.