Wondering if your Hubby Action ran successfully? Hubby Action Logs make it easy to see what happened behind the scenes!
When you create an automated Hubby Action, you want to know it's working as expected. Whether you're troubleshooting an Action that didn't run the way you anticipated or simply checking that everything is running smoothly, Hubby Action Logs can help.
These logs show when your Actions were triggered, what information Hubby received, and how Hubby responded.
How to Access the Hubby Action Logs
For step-by-step instructions with screenshots, see the Step-by-Step section at the bottom of this article.
Step 1: From the New Interface, go to Business Tools > Hubby Actions
Step 2: Click the Hubby Action you'd like to review
Step 3: Scroll to the Webhook Triggers section
Step 4: Click the Log icon (three stacked horizontal lines)
Step 5: Click an event to review the activity
Step-by-step to Create a Hubby Action
Step 1: From the New Interface, click the Business Tools tab on the left-hand navigation menu. Then, select the Hubby Actions tab.
Step 2: In your list of Hubby Actions, click on the Hubby Action that you would like to review.
Step 3: In the Hubby Action Details drawer, locate the Triggers section.
Step 4: On the trigger, click the time icon - it is the clock with arrow to the far right of the trigger.
Step 5: Click on a specific Event to review the details and verify that your Hubby Action is performing properly.
Understanding the Event Log
The Event Log displays a history of events associated with your Action's trigger.
Each entry contains information to help you understand when an event occurred and whether Hubby processed it.
Here's what you'll see:
- Date/Time: When the notification attempt was recorded.
-
Event: The event that triggered the Action, such as
order.addwhen a new order is placed. - Response: The response status, including the attempt number and response code.
- URL: Identifies the Hubby Action associated with the event.
Note: Notifications that share the same event type and endpoint URL may appear together in the Event Log.
Finding a Specific Event
If you're looking for a particular event, use the filters at the top of the Event Log:
- Search Details: Search for information associated with an event.
- Max Lines: Adjust how many log entries are displayed.
- Before: Narrow the results to events before a selected date and time.
Reviewing Individual Action Results
Want to know exactly what Hubby did when an Action was triggered? Click on an Event Log entry to open the Notification Attempt details. This view provides additional information about the Action's execution, including:
Event Information: Displays the event type, date, time, and response status.
Endpoint URL: Identifies the Hubby Action that was triggered.
Request Payload: Shows the information provided to Hubby when the event occurred. For example, an order.add event may include order details such as the property address, products ordered, client information, and appointment details.
Response: This is where you'll find the most helpful troubleshooting information!
The Response section shows Hubby's explanation of what happened when the Action ran. Depending on the results, it may explain:
- What tasks Hubby completed successfully.
- Why Hubby determined that no action was needed.
- Whether part of the requested Action could not be completed.
- What prevented Hubby from completing a task.
Understanding Response Statuses
You may notice a green 200 response status displayed in your Event Log. A 200 response indicates that the Hubby Action request was processed and a response was returned.
However, a 200 response does not necessarily mean that every task within your Action was completed successfully.
For example, Hubby might successfully process an Action but be unable to send a requested email because the sender email address hasn't been verified.
In this situation, the Event Log could still display a 200 response, while the Response section explains why the email wasn't sent.
Tip: Always check the Response details when troubleshooting. They provide much more information than the response status alone.
Understanding Response Statuses
Scenario 1: Hubby Completed Part of an Action
Let's say you've created an Action with these instructions:
When an order is placed that contains a drone or aerial product, email Felix so the fly zone can be verified. Then, tag the order 'drone unverified'.
After an order is placed, you check the logs and see that Hubby:
- Successfully identified an aerial product.
- Added the "drone unverified" tag.
- Couldn't send the email because a sender address hadn't been verified.
What to do: Review the explanation in the Response section and resolve the reported issue. In this example, you'd need to verify your Business email address under Business → Email Settings.
Scenario 2: Hubby Didn't Make Any Changes
Sometimes an Action runs successfully but doesn't need to do anything.
Using the same drone example, imagine a new order is placed that doesn't contain any drone or aerial products.
The Event Log might show:
No action taken. The order does not contain a drone or aerial product.
This is expected! Hubby reviewed the order, determined it didn't meet the conditions of your Action, and appropriately skipped the requested tasks.
What to do: No changes are needed if Hubby correctly followed your instructions.
Scenario 3: Hubby Isn't Following Your Instructions
If an Action runs but doesn't behave the way you expected, start by reviewing its Response.
Check whether Hubby misunderstood your instructions, lacked the information needed, or encountered an issue completing the request.
You can then return to your Hubby Action Details and review:
- Action Instructions: Are your instructions clear and specific?
- Triggers: Is the correct event configured to start the Action?
- Status: Is your Action active?
Make any necessary adjustments and click Save Updates.
Understanding Response Statuses
A few helpful things to remember:
- Start with the Response. This is often the quickest way to understand what happened.
- Check the Request Payload. Make sure Hubby received the information needed to complete the task.
- Review your conditions. Sometimes an Action correctly runs without making changes because its conditions weren't met.
- Look for partial success. Hubby may complete one part of an Action while encountering an issue with another.
- Test after making changes. Run the updated Action again under appropriate test conditions and review the results.
Important: Hubby Action runs are not automatically retried. If an Action couldn't complete a task, correcting the underlying issue won't automatically rerun that previous event.
For any additional questions, our Support team is ready to help you!
Call: (509) 515-3338
Email: Support@HDPhotoHub.com
Or use the chat button in your account for live assistance.