Currently, Absorb doesn't support error messages or pop-up prompts to inform the admin user when there is a conflict within the course settings while you are creating and editing it. This can result in confusion and wasted time contacting Absorb Support to identify the issue and fix the settings conflict.
For example, my team ran into an issue recently where when adding a task object into the course content section, the entire course would lock up and freeze completely, leaving us to refresh the webpage and redo all settings except for adding in the task.
After several emails back and forth with Absorb Support, we found that due to us having the Mobile App Download setting enabled, we weren't able to also add a task along with this. There was no prompt to inform us that these two settings weren't able to be enabled at the same time, the webpage would just lock up and freeze. Funnily enough, this issue still persists to this day and hasn't been fixed even after informing support about this...
Another example my team recently went through was the publish/quick publish buttons were disabled/greyed out and could not be clicked on. It was locked off and we were unable to save any new settings for this course as the publish/quick publish buttons would disable themselves immediately upon opening the course.
Again, after emailing Absorb Support we found that due to us having the Proctor toggle enabled with the Other option selected without any additional accounts used for this Other section as a proctor, this setting was causing the publish buttons to disable themselves. Now keep in mind, that this setting was already enabled and set when we transitioned this course from our old LMS to Absorb and it had no issues defaulting to this setting and saving automatically.
If Absorb had an error prompt message which mentioned the conflict within the settings for both of these issues, it would have saved several hours of emailing and testing as it would be plainly explained that X setting can not be enabled when Y setting is also enabled. This should be standard for any software, and I'm quite surprised this is such a large omission for the LMS itself.