Could someone please help me?
I’m using a bot to create PDF files of quotations.
The PDF files I created up until yesterday open normally, but the PDF file I created today displays HTML and won’t open.
However, it is created and can be opened directly from Google Drive.
I haven’t changed any settings, but has there been a change in specifications?
I haven’t changed the default app folder either.
Please contact Support for help with this if you haven’t already.
Thank you, @Steve. I inquired about it, but unfortunately, it seems there are no experts available to answer, and it will take some time.
It’s frustrating because the entire company uses it every day.
Hello @Maki,
I found a post that I believe reflects the same issue you have and how they resolved it:
Let me know if this helps please
Please post a screenshot of the HTML and the complete configuration of the task that generates the PDF.
Thank you, @Steve and @Jose_Arteaga, for your kind assistance.
I haven’t changed any settings since checking this issue yesterday, but I was able to open a PDF file I created today without any problems.
However, the file I created yesterday still won’t open.
This doesn’t seem to be an issue with my environment.
I’ll wait for a response from support.
Have you tried re-generating this file? There might have been a one off or temporary issue that corrupted that particular file.
Thank you, @WillowMobileSys.
Due to a rule issue, I cannot recreate the file, so I will try copying the app and then recreating it.
Incidentally, it’s still unstable today; some files open, but others don’t.
Also, I received the following message from support:
Our engineering team is currently investigating a known issue with the backend rendering service responsible for generating and processing these PDF files. We have found that intermittent instability in this service can cause the app to fail to display the file entry, even if the file itself exists in Drive.
Engineers are actively working to resolve these intermittent failures. On June 17, 2026, they confirmed that further analysis is being conducted to identify the root cause of these ongoing display issues.
@Maki Did you ever get a resolution to this?
Hello, @Steve
It’s still unstable, working some days and not others.
I received the following message from support last week:
I am reaching back with good news. The product engineering team has identified the issue and is working towards a resolution. No ETA has been provided, however the fix will be deployed immediately.
As soon as I know anything else, I will update you again!
Hello @WillowMobileSys
I tried regenerating the PDF file that I couldn’t open from the copied app using the bot, but the same problem occurred and it still wouldn’t open.
Are you trying to open the file directly from your cloud storage (e.g. Google Drive)? Does it exist and Will it open that way?
If not, then there is some issue with generating the file. Look at the Automation Monitor to see if any errors are being recorded.
If all that seems fine then we need to start looking at the automation step and the actual template being used to generate the file. NOTE: If there are template issues preventing the generation of the file, these are normally reported as errors in the Monitor.
@Maki Was this ever resolved?
I had the same problem with all my files.
The issue was caused by the folder path ending with a /. It looks like AppSheet changed something recently, and now if the file or image path ends with /, AppSheet does not treat it correctly as the final folder path.
For newly saved files, AppSheet may even create a new folder inside the expected folder. But the issue can also affect older files: even if the path is technically correct and the file exists, the file do not open until you remove the trailing /.
The fix was simply to remove the final / from all folder paths.
For example, instead of:
Folder X/
use:
Folder X
After removing the trailing slash from my paths, both new and existing generated files opened normally again.
Hello @WillowMobileSys
Actually, the file exists and opens fine directly from Google Drive.
The issue is that I cannot open it using the “External: open a file” Action.
I checked the Automation Monitor, but there were no errors recorded.
Also, this issue doesn’t happen with all PDF files—only some specific PDFs fail to open.
Hello, @Steve
Last week, I received the following message from support:
"The engineers reached back stating they pushed a bunch of configuration updates which should have resolved the issue. They kindly ask you to test out and let me know if the issue persists right now.
I look forward to your reply!"
I replied as follows:
"The files I created today can be opened for now.
However, some files I created before yesterday can be opened, while others cannot, even though they were created on the same day. The behavior is unstable.
Therefore, I can only say “for now.”"
Then, I received the following message:
"That is very fair, thank you a lot for the prompt reply with confirmation of what is happening.
I have updated the engineers. They might request some more details from your side however I will let you know if they do!
Please standby for updates."
Since the issue doesn’t seem to have reoccurred so far, I guess we can consider it resolved for now.
Hello, @Enginapps,
The File Folder Path for the “Run a task” in the Bot is set to “/Quote/”.
Is this incorrect?
You need to remove the last slash.
“/Quote” - that means the file is saved in Quote folder.
“/Quote/” - the file will be saved in “/Quote/New Folder/quotename.pdf” but in your database the file column will have the correct path “/Quote/quotename.pdf” - that’s why you get the black error screen when opening the file.