Rohan Pokharel

Hi @millehogr,

Thank you for your patience while we investigated this further.

Based on the information you provided and our findings, we suspect the issue may be related to background processing for the Google action, particularly when used alongside the Password Protected plugin.

Could you please try disabling Background actions under Automator > Settings > Advanced, and then run then retry the recipe run from the log (or trigger a new recipe run)?

If the recipe works after disabling this setting, it would confirm that the issue is related to loopback requests being blocked.

In that case, you can either:

• Whitelist the endpoint /wp-json/uap/v2/ in the Password Protected plugin settings, or
• Keep Background actions disabled (this is generally fine for low-volume sites)

Background actions are used for processing tasks asynchronously, but in some cases, they can be affected by restrictions like login protection or blocked loopback requests.

Please let us know what you observe after trying the above steps.

Regards,
Rohan

Hi @millehogr,

Thank you for the detailed report and sorry for the trouble caused.

It sounds like the issue is specific to the Google Sheets action. The debug traces point to the uap_before_action_executed filter and throttle error, so the action is not completed although it doesn’t show the actual reasons.

The “Not completed” status usually indicates recipe corruption, mainly if we directly modify a recipe without drafting first which can sometimes cause issues, or we’ve seen that if the Google Sheet contains invalid names and the target Spreadsheet does not follow standard naming convention or the worksheet or column headers have special characters like quotation marks or similar.

I tried to reproduce on my end but I see the recipe completes successfully. See this reference: https://cleanshot.com/share/Gsrv6xjZ

The system status looks fine and while the anomaly you mentioned with the DB prefix can be relevant, can you please try to isolate that with these steps?

1. You mentioned you removed the action and tried it but can you try to create a new recipe itself if not done already and cross-check any potential corruption.
2. Cross-check with another spreadsheet and see if the issue persists. The target spreadsheet itself can cause failures. Worksheet and file names should start with at least 4 non-integer characters. Google Sheets has trouble with names that don’t follow this rule (e.g., TE12 and AXB123 may fail, TEIR12 and AXBC1 are fine, and certainly anything that starts with MORE than 3 letters is fine). Also, in the column headers like quotation marks and special characters can be problematic, so try to check with a simple sheet so we can rule out Sheets-side issues.

If the issue persists after the above checks, please also share the actual JSON log, and any other errors relevant. You can upload them to your Google Drive or similar and attach the link here.

Let us know and we will investigate further.

Regards,
Rohan

Hi @jarledb,

It’s been a while since we heard back from you. We’ll mark this ticket as resolved for now, but please reply if you still have problems or any questions.

Regards,
Rohan

Hi @davifnr,

Thank you for the details, and we’re sorry for the trouble caused.

While we couldn’t reproduce the issue on our end, it may be related to your environment. Could you please ensure you’re using the latest version of Uncanny Automator (7.1.0.1)? This update includes several performance improvements that might be related to what you’re seeing.

If you’re already on the latest version, and although your troubleshooting steps look good, just to verify, please share the following details so we can investigate further:

1. Go to Automator > Status in your dashboard, click “Get system report,” and copy the system info and share it with us.
2. Screenshot of the recipe with both the trigger and action expanded.
3. Go to Automator > Logs or click the “View logs” link next to “Completed runs” in the recipe editor sidebar. Then select “Details” for the specific log entry, and click the download icon at the top of the modal (see here: https://tinyurl.com/2ccepbq8). Please send us the downloaded JSON file for further review. You can upload it to Dropbox, Google Drive, etc and share the link.

Once we have these details, we’ll take a closer look.

Regards,
Rohan

Hi @seanalreadyheard,

Sorry for the inconvenience caused by these 503 errors and server overload.

It seems the async job queue spiked from the post publish triggers, but since this appears to be tied to the Pro version, could you please open a support ticket by logging into your Automator account and submitting the request here?

Also please attach the System status report (under Automator > Status), exact error log entries, and screenshots of the CPU spike.

We will then investigate and assist you further. Thank you for your patience!

Regards,
Rohan

Hi @seanalreadyheard,

To have the featured image show up as an actual image in the Bluesky post, you’ll need to use Media embed → External media (not Website).

When you choose Website, Bluesky will try to embed a social card or website preview for the URL you provide, so it won’t post your featured image as an attached image.

In the External media field, insert the token “Post featured image URL” (from the trigger tokens). That should embed the featured image itself. Note that it should meet Bluesky’s requirements, for example, images must be 1 MB or smaller, JPEG or PNG format and ideally have a 1:1 aspect ratio.

Please try this and, if you see any issue, let us know exactly what happens (for example, what appears in the recipe log, any error messages, and how the image is being linked).

Regards,
Rohan

Hi @pat_martinez,

We haven’t heard back from you for a while, so we assume this issue has been resolved. We’re marking this ticket as resolved for now.

Please feel free to reply here or open a new support request if you need further help.

Regards,
Rohan

Hi @dmitrydzh,

We haven’t heard back from you for a while, so we assume this issue has been resolved. We’re marking this request as resolved for now.

Please feel free to reply here or open a new request if you need further help.

Regards,
Rohan