As a regular user of Matillion, I’ve always appreciated the flexibility and powerful features it offers. Recently, my team upgraded to the latest versions of Matillion (1.75.0 and 1.75.8) from version 1.68.21, which we found to be more user-friendly and stable. While the new versions introduced some improvements, but we’ve faced several challenges that have impacted our workflow.
I’d like to share some of these issues with the community to see if others are facing the same problems and to get feedback on whether these are bugs or intentional features in the newer versions. Here’s a breakdown of the three major problems we’ve encountered:
1. Deleted Components Reverting Back
One of the most frustrating issues we've encountered is that when we copy components from one transformation job to a new one and later delete some of those copied components, they mysteriously revert back to their original positions—even after saving the job. We expected that once a job is saved with the deletion, those components should be permanently removed.
Question for the community:
Has anyone else encountered this issue in versions 1.75.0 or 1.75.8? Is this an intentional feature or a bug related to saving the state of jobs?
2. Column Name Insertion While Checking Samples
In version 1.68.21, when checking samples using a filter, we could easily load the needed column names by clicking the arrow mark next to them. However, in the latest versions, this behavior seems to have changed. Now, we have to double-click the column name to insert it, but the arrow mark is still present, which adds confusion.
Question for the community:
Has this behavior been intentionally changed, or is it a bug related to the arrow mark functionality? Is there a more efficient way to insert column names in the newer versions?
3. Schedule Timing Mismatching
In the new versions, we’ve encountered an issue where scheduled jobs run successfully but don’t always appear in the task history as expected. Additionally, the same schedule sometimes runs at different times than what was specified, creating confusion about the actual run times.
Question for the community:
Has anyone else seen this discrepancy with the schedule timing and task history in Matillion versions 1.75.0 or 1.75.8? Is this a known bug, or is there a new scheduling mechanism that we’re missing?
Final Thoughts
Our experience with Matillion has generally been positive, but these recent issues have added some friction to our workflow. We’re eager to hear from the Matillion community to better understand if these are bugs that should be reported or features, we need to adapt to. Any tips or insights are welcome!
Looking forward to the community’s feedback!