Trigger-based orchestrations

Yes I know. But re-adding is not bullet proof solution. There is very high risk that some developer forget it and we will have next day impacted data for bussiness. So I will rather stay with our stable workaround.

Or possibly re-add the table that has been worked on - this should reset the state as well I think.

@Petr Šimon I think there has been an api call to clear the state - in this way you could clear it at 19:00 and then both tables would be marked as updated and trigger the orchestration at 20:00.

I am asking tech if they can dig the api call and confirm this works. 

Another scenario from our experience:

• import of "invoices" runs each day at 19:00
• import of "customers" runs each day at 20:00
• We expect the trigger to fire at 20:00 when the customers are imported for the day

Now examine what happens:

• Somebody changed/developed customer transformation yesterday so table customer is changed.
• The trigger registers import of "customers" at 22:00 previous day
• The trigger registers import of "invoices" at 19:00 current day
• the trigger fires!
• The trigger registers import of "customers" at 20:00 current day
• From now it is always triggering at 19:00 without current customer data. There is no easy and reliable way how to prevent this situation currently. So because of that we have complains. :-)

Hi all,

So I poke around and got a message from our tech, who were poking in after similar reports:

Problem might be in the following scenario:

• import of "customers" runs each day at 10:00 and 20:00
• import of "invoices" runs each day at 19:00
• I expect the trigger to fire at 20:00 when the customers are imported for the day

Now examine what happens:

• It's 09:00 and I created a trigger for customers and invoices.
• The trigger registers import of "customers" at 10:00
• The trigger registers import of "invoices" at 19:00
• the trigger fires!

user complains it fired for "any" table

• although it correctly made sure that it fired when all the tables in it have been updated
• it had customer update from morning and invoices update from evening, didn’t need to wait for evening customers import

I agree with Vít Gabrhel. We faced almost same problem few months ago. Currently we are using workaround with custom transformation which checks, whether both tables was changed during last day. If yes then we are creating single table which is used as orchestration trigger.

just to add to this though, the behaviour should be

When a selected table is updated, the scheduler checks all other selected tables for updates. Once all selected tables are updated since the last orchestration execution, the orchestration will run again.

https://help.keboola.com/orchestrator/running/#event-trigger

if you witness other behaviour, please contact support with details - it shall be imho bug, not a feature!

Hi Vitku,

I believe this belong to a feature suggestion, currently available through the button within the platform. I am adding @Kristyna Kaucka to grab it from here then!