Impact of using DisableConcurrentExecution with timeout of 0

Can anyone clarify what the behavior of the DisableConcurrentExecutionAttribute will be when the timeout is 0?

I had a look at the source and the timeout parameter is being passed directly through to the sp_getapplock stored procedure - the documentation for this says that if the lock timeout is 0 then an error is raised if the lock cannot be acquired, rather than waiting.

Let’s say I have a job which runs every 3 minutes, and one particular job runs for 11 minutes, meaning 3 other jobs are queued while the first one is running - with this attribute applied for a timeout of 0, the other 3 jobs should fail immediately, will Hangfire attempt to retry them or will this just result in those jobs being discarded?