usman
Member
- Your Workflow URL
- https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjYwNTY1MDYzMjA0MzA1MjY1NTUzMjUxMzci_pc
- Your Task History ID
- IjU3NjUwNTZiMDYzMzA0M2M1MjZiNTUzMTUxMzc1MTY2NTQzNjBmMzki_pc
- Consent to Access & Modify
- I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.
### Problem Description
Hello Pabbly Team,
I’ve set up an automation workflow in Pabbly Connect where:
1. **Trigger**: *Google Business Profile → New Review (Multi Location)*
2. **Action**: *Google Business Profile → Create Reply (Legacy)*
The flow generally works, but intermittently the **Create Reply step fails with a 404 NOT_FOUND error** even though the review details are being pulled correctly from the trigger step.
- In some runs, the reply is created successfully.
- In other runs, I see:
Error Code: 404
Error Message: Requested entity was not found.
Error Status: NOT_FOUND
I am mapping `review.name` directly from the trigger output into the Reply step. I am **not hardcoding account or location IDs**. The same setup works for most reviews, but fails randomly for others.
---
### Actuals / Observations
- Trigger step provides `review.name` like:
accounts/{accountId}/locations/{locationId}/reviews/{reviewId}
- The failing reply step endpoint matches the above, but still throws 404.
- It looks like the connector might be attempting the reply **before the review is fully available via the API**, or there’s an issue when handling multiple locations.
- In production, only some reviews fail, others succeed under the exact same setup.
---
### Request
Could you please:
1. Check why the **Google Business Profile → Create Reply (Legacy)** action intermittently returns 404 despite correct mapping.
2. Suggest a reliable workaround (e.g., retry, delay, or using “API by Pabbly” with custom request).
I have attached screenshots of:
- Successful run
- Failed run (404 error)
- My workflow setup showing how I mapped `review.name`
- Task history showing both successful and failed executions
Hello Pabbly Team,
I’ve set up an automation workflow in Pabbly Connect where:
1. **Trigger**: *Google Business Profile → New Review (Multi Location)*
2. **Action**: *Google Business Profile → Create Reply (Legacy)*
The flow generally works, but intermittently the **Create Reply step fails with a 404 NOT_FOUND error** even though the review details are being pulled correctly from the trigger step.
- In some runs, the reply is created successfully.
- In other runs, I see:
Error Code: 404
Error Message: Requested entity was not found.
Error Status: NOT_FOUND
I am mapping `review.name` directly from the trigger output into the Reply step. I am **not hardcoding account or location IDs**. The same setup works for most reviews, but fails randomly for others.
---
### Actuals / Observations
- Trigger step provides `review.name` like:
accounts/{accountId}/locations/{locationId}/reviews/{reviewId}
- The failing reply step endpoint matches the above, but still throws 404.
- It looks like the connector might be attempting the reply **before the review is fully available via the API**, or there’s an issue when handling multiple locations.
- In production, only some reviews fail, others succeed under the exact same setup.
---
### Request
Could you please:
1. Check why the **Google Business Profile → Create Reply (Legacy)** action intermittently returns 404 despite correct mapping.
2. Suggest a reliable workaround (e.g., retry, delay, or using “API by Pabbly” with custom request).
I have attached screenshots of:
- Successful run
- Failed run (404 error)
- My workflow setup showing how I mapped `review.name`
- Task history showing both successful and failed executions