We had a case recently when a source table became 'unavailable' to QR. (Full Load Task) To be clear, through permissions on the source side, QR was unable to see table at all. The result was that the table simply stopped replicating and went unnoticed for some time.
If one visually compares the "Patterns & Selected Tables" list, the table is listed. On the "Full Table List" the table is not listed. That's the only evidence you see.
So is there a way to detect differences between the required tables and the ones actually recognized by QR ?
@Heinvandenheuvel In my experience when the task is created manually or via automation which means that the tables were not selected by going into the Table Selection tab in the UI in that case the non existent table will show up in the "Patterns and Selected Tables" view and that's sort of a reference to the tables configured in the json. TheFull Table List is what qlik can truly connect to on the database. The error that I'm talking about will only show up during the first execution and it may just be a warning( might need verbose source unload logging). I had experienced this issue a while back (2 years ago) so don't recall all the ways and means using which I got to diagnose this issue but solution was to always refer the Full Table List list to verify the tables that Qlik has access to.
