HI, we are using Tidal 6 and we observe that some times SAP jobs get stuck in "Launched" status for about 15 minutes before getting active.
what could be the possible reasons ?
yeah, that what i do now a days, when we are unable to cancel a job stcuck in launched state, we just disable the connection, let the job instance got to orphaned state and then mark it as success.
then enable the connection