Mysql data is not getting triggered

Hi @Crudoimage,

Please try establishing a new connection with your MySQL database and see if that fixes your issue.

I did. But everything same. It did not work. I checked the database, it updated but no sign in Pabbly

Hello @Crudoimage,

The workflow seems to be getting triggered, refer to the attached screenshot.

Could you confirm if any records are still being missed? If so, please share specific details to help us investigate further.

Again same error. It is not working properly again.

Hi @Crudoimage,

Your workflow appears to be getting triggered (please refer to the attached image for more details). However, if there are any rows that may have been missed, kindly provide us with unique details for those specific records. This will help our team investigate the matter further.

Looking forward to your response.

It is automating the process on 12:33 am , I have not set this time to trigger any where

Hello @Crudoimage,

Please allow us some time to investigate the issue further. We will provide you with updates as soon as we have more information.

Thank you for your patience and understanding.

Okay

Hello @Crudoimage,

The issue appears to be related to the time zone difference. The records from SQL are in UTC, while your Pabbly Connect account is set to Asia/Kolkata. This might make it seem like workflows are running late.

However, since your workflow polls the data at a 10-minute interval (and can go up to 30 minutes max), there will generally be no more than a 10-minute difference between the record's creation time and the workflow's trigger time.

Let us know if you need further clarification!

check

Hello @Crudoimage,

Thank you for sharing the screenshot. It seems the time zone displayed is based on the localhost rather than the server where your database is hosted.

Could you please execute the query directly on the server where your database is hosted and share a screenshot with us? This will help us better understand the issue.

Thank you for your cooperation!

Our server is running WHM & cPanel, and we are using phpMyAdmin to manage the database. Please find below the screenshot showing both the Server Time and MySQL Time

One more

Hello @Crudoimage,

Could you please confirm if you're manually adding data to MySQL or if SQL is auto-filling the created and updated dates?

If SQL is auto-filling these fields, could you provide us with a screenshot or a short screen recording showing the format and time zone of the dates entered by SQL? This will help us investigate the issue further.

Thank you for your cooperation!

Auto Created while task created.

Hello @Crudoimage

Could you please provide us with a screenshot that includes the dates and additional details from the rows? This will help us compare and verify if there is a time difference. Also, please let us know if the created and updated date and time are added as per Asia/Kolkata timezone or as per any other timezone.

The current screenshot does not provide sufficient information for us to check. It would be helpful if you could share the details as shown in the example screenshot below.

PDF version and CSV as Zip

Hello @Crudoimage,

The file you’ve shared contains data with a start date for 2023, but since we only store task history for the last 15 days, we cannot use that data for comparison. Please provide the most recent rows so we can assist you more effectively. Without the correct details, it will be challenging for us to resolve the issue.

Also, please let us know if the created and updated date and time are getting added by the system as per Asia/Kolkata timezone or as per any other timezone.

Looking forward to your response.

system as per Asia/Kolkata timezone

Same bulk Process issue. Not triggered base

Hello @Crudoimage,

Upon reviewing the issue, we found that the SQL API is sending the responses in UTC time zone, which is causing the time differences you're experiencing in your workflow. Despite this, the workflow itself is working fine.

To capture the responses in the Asia/Kolkata time zone, you would need to contact the SQL team to address this time zone discrepancy.