I contacted support, and they informed me that the issue is known and currently being worked on. However, they couldn’t provide any specific time frame for a resolution.
That's a real shame as autoactions are a core feature. Does anyone have any suggestions for a workaround?
PENDING auto action status too long
-
niallcollinson
- Posts: 6
- Joined: Fri Mar 15, 2024 11:17 am
Just wanted to chime in again to express the extent this can disrupt operations. Currently I'm spending around 30mins - 1 hour ensuring all the check-in information has been sent to bookings. This is an extremely tedious process if you consider we manage over 100 listings. I'd consider this one of the biggest issues wasting my time.
-
vincent marquet
- Posts: 1
- Joined: Mon Jul 21, 2025 11:21 pm
Same for me
I do not understand why some Beds24 accounts are not impacted and as a result the designated Auto Actions are triggered instantaneously and why starting from my Confirmation message, it is not triggered immediately, sometimes after a few hours (maybe 4 hours later) and sometime not executed at all
Even managing 15 listings, critical core issue
I do not understand why some Beds24 accounts are not impacted and as a result the designated Auto Actions are triggered instantaneously and why starting from my Confirmation message, it is not triggered immediately, sometimes after a few hours (maybe 4 hours later) and sometime not executed at all
Even managing 15 listings, critical core issue
-
melbury.elliot
- Posts: 7
- Joined: Fri Jul 19, 2024 11:12 pm
I would also like to reiterate how frustrating the lack of specific timing is on Auto Actions.
There is a discrepancy of anything up to 12 hours from one day to the next, even though the bookings being triggered are all in the same state (and the Auto Action shows 'Pending'). On a few occasions, guests have contacted us to say they've not received their check-in instructions, which is not a good impression from us.
It seems to make no difference what "Trigger Time" is set to. The only one that works is when Trigger Event = Booking and Trigger Time = Immediate. Those messages always fire, but the timing of anything related to pre-arrival, post-booking, or post-departure seems to be complete random luck.
For messaging at least, timing is absolutely critical, hence both Booking and Airbnb offer scheduling for message templates on their own platforms.
I would appreciate an official statement from Beds24 to even acknowledge the operational impact this is having.
There is a discrepancy of anything up to 12 hours from one day to the next, even though the bookings being triggered are all in the same state (and the Auto Action shows 'Pending'). On a few occasions, guests have contacted us to say they've not received their check-in instructions, which is not a good impression from us.
It seems to make no difference what "Trigger Time" is set to. The only one that works is when Trigger Event = Booking and Trigger Time = Immediate. Those messages always fire, but the timing of anything related to pre-arrival, post-booking, or post-departure seems to be complete random luck.
For messaging at least, timing is absolutely critical, hence both Booking and Airbnb offer scheduling for message templates on their own platforms.
I would appreciate an official statement from Beds24 to even acknowledge the operational impact this is having.
-
lesleywoermeijer
- Posts: 487
- Joined: Wed Dec 28, 2016 2:20 pm
Auto Actions are not designed as real-time actions. They are sent in batches at times so we recommend you set your triggers to allow for this.
But we hear you — delays in auto actions and webhooks are frustrating, and we take this seriously.
Behind the scenes, we’ve been working hard on a major infrastructure upgrade scheduled for later this year. This is not a minor fix — it’s a significant investment aimed at transforming system performance and ensuring faster, more reliable automation for all our users.
Your experience matters to us, and this upgrade is a direct response to feedback like yours. We truly appreciate your patience and continued support as we roll out the improvements you deserve.
But we hear you — delays in auto actions and webhooks are frustrating, and we take this seriously.
Behind the scenes, we’ve been working hard on a major infrastructure upgrade scheduled for later this year. This is not a minor fix — it’s a significant investment aimed at transforming system performance and ensuring faster, more reliable automation for all our users.
Your experience matters to us, and this upgrade is a direct response to feedback like yours. We truly appreciate your patience and continued support as we roll out the improvements you deserve.
-
benidormengine
- Posts: 39
- Joined: Mon Nov 02, 2020 11:00 am
- Contact:
Thank you for your update!!
It's understandable that it's not real-time, but having delays of 12 or 20 hours in the execution of auto-actions is a different matter.
In any case, we appreciate that you're taking steps to hopefully significantly improve this problem.
It's understandable that it's not real-time, but having delays of 12 or 20 hours in the execution of auto-actions is a different matter.
In any case, we appreciate that you're taking steps to hopefully significantly improve this problem.
This is kind of a worrying issue because ideally auto-actions would be literally thousands of times faster to be well-suited for many common uses (e.g. to achieve 20 seconds instead of 20 hours would require them to be three thousand six hundred times faster). Currently if I was to, for example, use an auto-action to change a booking from Inquiry to Confirmed once payment was received, any number of people could have paid for and double-booked the same room before the auto-action noticed the first payment and confirmed the booking. (Additionally, it would often fail to trigger before check-in.)
If, on the other hand, I set the booking to Request so double-bookings were avoided and intended to give the requester an hour to pay, the room would be blocked for ~20 hours before the one-hour auto-action finally triggered and cancelled the request.
This issue has been ongoing for months now. What is the bottleneck for auto-actions that's unable to be scaled up? I'd be willing to pay extra for auto-actions that triggered within a reasonable time. I have trouble understanding how every auto-action my own property needs each day would add up to much more than a second of CPU time?
If, on the other hand, I set the booking to Request so double-bookings were avoided and intended to give the requester an hour to pay, the room would be blocked for ~20 hours before the one-hour auto-action finally triggered and cancelled the request.
This issue has been ongoing for months now. What is the bottleneck for auto-actions that's unable to be scaled up? I'd be willing to pay extra for auto-actions that triggered within a reasonable time. I have trouble understanding how every auto-action my own property needs each day would add up to much more than a second of CPU time?
-
lesleywoermeijer
- Posts: 487
- Joined: Wed Dec 28, 2016 2:20 pm
As already confirmed. Behind the scenes, we’ve been working hard on a major infrastructure upgrade scheduled for later this year. This is not a minor fix — it’s a significant investment aimed at transforming system performance and ensuring faster, more reliable automation for all our users.
Our review of multiple users and auto actions has identified several opportunities for significant performance improvements, which will help reduce the overall impact on actions, bookings, and properties.
General points :-
* OUTGOING EMAIL SERVICE - To send emails you need to have a working Outgoing email service. If you receive a notice it is failing then go to Settings > Account > Outgoing email and fix it.
There is no fall back, the emails will not be sent, your guests will not receive their emails. Causing delays to every auto action in your account.
* OFFSET - Trigger time + 17hrs, this is the first time the auto action could be checked and potentially added to a batch for processing. There is no guarantee of the timing due to the volume of auto actions/bookings. Consider this when using the Offset.
RECOMMENDATIONS :-
* Do not duplicate auto actions for each property, use the Property Templates [PROPERTY TEMPLATE1-8] and [ROOMTEMPLATE1-8] in your communications.
Create one set of auto actions and using the Property/Room Templates you can manage the specific content.
Easier to manage and processing.
* GROUPS - Auto actions should trigger on some not all properties.
Use GROUPS, in Settings > Properties > Description > Display > Group Keywords, create a Group for the property, properties can belong to multiple groups.
In the trigger tab, use 'Send only to Property groups' XX
* SAME DAY BOOKINGS - checkin details.
Consolidate all of the auto action into 1 auto action for Same day booking/arrivals.
Same day - Trigger Event = Booking, Trigger time = Immediate, Between booking and checkin = 0 and 0.
Standard bookings - Trigger Event = Checkin, Time window = -1 day, Between booking and checkin 1 and 999
When using a negative value to trigger auto actions for Booking Event = Checkin or Checkout, use the same value in Trigger time/Time window.
Trigger time = -3days, Time window = 3 days. The clock starts at 3 days before and checks upto 3 day until all rules are met in the Trigger tab.
* TIME WINDOW - use the correct value, minimise the number of auto actions you have with Time window = +365 days, why do you need the auto action/booking to be checked for 365 days.
Exception to this would be if you want to trigger an action for Cancelled bookings, then Trigger Event = Booking, Trigger time = Immediate, Time window = 365 days as the cancellation can be any time.
* SEQUENCE - Manage the order of the auto actions based on priority and guest -v- internal messages.
Sending messages to the guest is more important than setting the colour flag, changing the Status - New to Confirmed, sending the booking notification to the Owner/Cleaning team (see point below regarding Internal Emails/Notifications)
Use Booking info codes to manage the sequence/order of the auto actions.
Auto action 1 -
Trigger tab :-
Trigger event = Booking
Trigger time = immediate
Time window = 1 day
Booking Info tab:-
Booking info code - FIRST
Booking info text = First auto action to trigger
Auto action 2
Trigger tab :-
Trigger event = Booking
Trigger time = immediate
Time window = 1 day
Any booking info code = FIRST
Booking Info tab:-
Booking info code - SECOND
Booking info text = Second auto action to trigger
* INTERNAL emails/Notifications - remove the need to trigger an auto action on every booking.
If you have multiple owners/cleaners and you need to send communications to Cleaning staff/owners with the booking details.
Send a report with the details, you can use one of the Standard Reports or create a Custom Report - REPORTS.
Create a Routine - Settings > Account > Routines.
Set the Routine rules, frequency, email details.
You have one owner/cleaner to send the details to, then you can use Routines, or you can use the Additional Email Notification setting in Settings > Account > Outgoing Email Service.
* BOOKINGS STATUS = NEW
Disable the use of Status = NEW in Settings > Properties > Booking Rules > Booking Status. Then bookings will be imported with Status = Confirmed.
*ONGOING ISSUES
If you have issues with auto actions and require assistance, then raise a ticket with the Support team provide the auto action id and booking ids and we will be happy to review and provide options for improvements.
Our review of multiple users and auto actions has identified several opportunities for significant performance improvements, which will help reduce the overall impact on actions, bookings, and properties.
General points :-
* OUTGOING EMAIL SERVICE - To send emails you need to have a working Outgoing email service. If you receive a notice it is failing then go to Settings > Account > Outgoing email and fix it.
There is no fall back, the emails will not be sent, your guests will not receive their emails. Causing delays to every auto action in your account.
* OFFSET - Trigger time + 17hrs, this is the first time the auto action could be checked and potentially added to a batch for processing. There is no guarantee of the timing due to the volume of auto actions/bookings. Consider this when using the Offset.
RECOMMENDATIONS :-
* Do not duplicate auto actions for each property, use the Property Templates [PROPERTY TEMPLATE1-8] and [ROOMTEMPLATE1-8] in your communications.
Create one set of auto actions and using the Property/Room Templates you can manage the specific content.
Easier to manage and processing.
* GROUPS - Auto actions should trigger on some not all properties.
Use GROUPS, in Settings > Properties > Description > Display > Group Keywords, create a Group for the property, properties can belong to multiple groups.
In the trigger tab, use 'Send only to Property groups' XX
* SAME DAY BOOKINGS - checkin details.
Consolidate all of the auto action into 1 auto action for Same day booking/arrivals.
Same day - Trigger Event = Booking, Trigger time = Immediate, Between booking and checkin = 0 and 0.
Standard bookings - Trigger Event = Checkin, Time window = -1 day, Between booking and checkin 1 and 999
When using a negative value to trigger auto actions for Booking Event = Checkin or Checkout, use the same value in Trigger time/Time window.
Trigger time = -3days, Time window = 3 days. The clock starts at 3 days before and checks upto 3 day until all rules are met in the Trigger tab.
* TIME WINDOW - use the correct value, minimise the number of auto actions you have with Time window = +365 days, why do you need the auto action/booking to be checked for 365 days.
Exception to this would be if you want to trigger an action for Cancelled bookings, then Trigger Event = Booking, Trigger time = Immediate, Time window = 365 days as the cancellation can be any time.
* SEQUENCE - Manage the order of the auto actions based on priority and guest -v- internal messages.
Sending messages to the guest is more important than setting the colour flag, changing the Status - New to Confirmed, sending the booking notification to the Owner/Cleaning team (see point below regarding Internal Emails/Notifications)
Use Booking info codes to manage the sequence/order of the auto actions.
Auto action 1 -
Trigger tab :-
Trigger event = Booking
Trigger time = immediate
Time window = 1 day
Booking Info tab:-
Booking info code - FIRST
Booking info text = First auto action to trigger
Auto action 2
Trigger tab :-
Trigger event = Booking
Trigger time = immediate
Time window = 1 day
Any booking info code = FIRST
Booking Info tab:-
Booking info code - SECOND
Booking info text = Second auto action to trigger
* INTERNAL emails/Notifications - remove the need to trigger an auto action on every booking.
If you have multiple owners/cleaners and you need to send communications to Cleaning staff/owners with the booking details.
Send a report with the details, you can use one of the Standard Reports or create a Custom Report - REPORTS.
Create a Routine - Settings > Account > Routines.
Set the Routine rules, frequency, email details.
You have one owner/cleaner to send the details to, then you can use Routines, or you can use the Additional Email Notification setting in Settings > Account > Outgoing Email Service.
* BOOKINGS STATUS = NEW
Disable the use of Status = NEW in Settings > Properties > Booking Rules > Booking Status. Then bookings will be imported with Status = Confirmed.
*ONGOING ISSUES
If you have issues with auto actions and require assistance, then raise a ticket with the Support team provide the auto action id and booking ids and we will be happy to review and provide options for improvements.