nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can not publish storymap

JosZwambach1

I get an error when publish a storymap. It says “Sorry there was a problem publishing your story” “Because of your account privileges, some sharing settings aren’t available. Contact your ArcGIS administrator for more information.”. Yesterday (1 dec) it works fine. I have also tested it with a simple cascade storymap and add a map. In the webmap one layer is added. What is wrong?

Find more posts tagged with

Accepted answers

oevans_storymaps

UPDATE: A fix has been deployed and publishing should now be working as expected again. Please let us know if you are still seeing issues.

We apologize for any impact this bug may have had on your work.

All comments

JonathanRoth1

I'm experiencing the same problem today. I can't publish changes to an existing storymap. I also tried creating a new storymap from scratch and can't publish it, either.

AGP

Same here.

When will this be fixed? I need to have my stories updated this week.

oevans_storymaps

We're looking into this high priority issue and will post an update here when we have more information. I apologize that this is affecting your experience at this time.

Anonymous User

Following.

oevans_storymaps

@AGP @JosZwambach1 -- We're unable to reproduce the problem with the stories we are testing, so this might have something to do with a specific piece of content in your story.

Are the stories public? If so, can you please share links to the stories you are having trouble publishing so we can look into this?

Erika1

I am having the same problem. When I add a webmap to the storymap it gives an error while publishing. When I remove the webmap again it has no problem with publishing. Can this be fixed? I would like to be able to add the webmap.

oevans_storymaps

@Erika1 -- I am able to publish stories with web maps, so it may be something specific about the map you are adding.

Can you share a link to the web map or its itemID? Please make sure the web map is public.

oevans_storymaps

All -- We're able to reproduce the issue. We haven't fully isolated the cause yet, but we're continuing to look into this. It appears to be related to the issue checker that looks at the sharing level of maps and layers in the story.

A workaround is to make sure all maps and layers in the story are already shared to the level to which you are publishing the story. For example, if you are publishing the story to Everyone, go to your ArcGIS Content page and make sure all the maps and layers in the story are already shared with Everyone, then return to the story builder and try publishing again.

Please post here if you are successful using this workaround. Workaround verified (reference).

There is a related issue publishing a story that contains a map with premium or subscriber content, regardless of the sharing level. See more information about that here.

We're working on a fix for this issue and will share more information here when it's available.

I'm going to mark this message as the solution so it bumps it up to the top of the thread for visibility, but we're still working on a resolution to this issue.

JosZwambach1

When I change the sharing of the service definition to Everyone (public), then I can publish the storymap. It had the deal with sharing level. Yesterday I got only a warning and could publish the storymap and now it is an error and I’m not able to publish the storymap.

JosZwambach1

Yes this is a workaround, but we don’t want to use the storymap outside our organization.

JacobBenner1

I am testing with a story that I could publish to Organization and Everyone with text only in the story. Then I added a map that included premium ESRI content, that was shared to Organization level. Attempting to publish that story failed with the same error. Here's the published version link (without map)

oevans_storymaps

@JosZwambach1 -- Thanks for sharing this information.

Please note that while the example gave was to share with Everyone if you are publishing your story publicly, the workaround works for sharing to the organization as well.

I believe a workaround is to make sure all maps and layers in the story are already shared to the level to which you are publishing the story.

oevans_storymaps

@JacobBenner1 -- Stories that have maps with premium or subscription content will also fail to publish at this time. We're working on a solution for this as well.

I haven't had a chance to test this yet, but I believe a workaround for using premium content would be to follow the instructions in the "Authorize subscriber layers" section of this article: Use ArcGIS Living Atlas subscriber content in public maps and apps (esri.com). I think this will circumvent the need for the story builder to authorize the content and possibly allow you to publish.

JacobBenner1

OK, Checked the map that I used in the story. It had some premium layers turned off, which I removed. I used only one layer with no restrictions. Shared the map to everyone, then shared the story with everyone, and it worked. Maybe it's something with the ESRI premium layers?

JacobBenner1

OK, Thanks. That's beyond my students' capabilities at this time, so I will wait for another resolution. I am sure they are experiencing the premium/subscriber content issue because many of them used Living Atlas layers in their maps.

oevans_storymaps

UPDATE: We are testing a fix in our dev environment now. We plan to deploy the fix later today.

I'll post another update here when there's more information to share.

RichieHolder

Hey Owen,

Could you give an estimate on when the fixes would be implemented? Would it be fixed by 2pm central time today?

oevans_storymaps

@RichieHolder -- There's a good possibility it will be deployed by 2pm CT / 3pm ET, but I can't confirm that just yet since we still are working on testing.

oevans_storymaps

UPDATE: We are planning to deploy a fix for this issue around 5:30pm ET today, Dec 2.

I apologize for the impact this issue may have had on anyone's workflows or plans.

oevans_storymaps

@RichieHolder -- Unfortunately, we can't provide the fix any earlier than 5:30pm ET today. That is the first window we could get to safely deploy our software patch.

oevans_storymaps

UPDATE: A fix has been deployed and publishing should now be working as expected again. Please let us know if you are still seeing issues.

We apologize for any impact this bug may have had on your work.

JosZwambach1

Thanks for the fix. It works.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.