I did find out that someone on our SAP BW team happened to modify and reactivate that specific process chain last night, so it seems that is likely what corrected the issue enabling the Tidal job to run properly this morning. If we encounter this iss...

Thanks for the reply.  I had one job that returned the message "No log id created for Process Chain" twice in one day.  Last night it ran normally without making any changes.  If it returns to error-ing out when attempting to run I will try recreatin...

Did you ever resolve this issue?  I have one SAP job that triggers a process chain that has had this error twice today.